Computer
US DOJ Sues To Block Hewlett Packard Enterprise's $14 Billion Juniper Deal
Read more of this story at Slashdot.
Google's 10-Year Chromebook Lifeline Leaves Old Laptops Headed For Silicon Cemetery
Read more of this story at Slashdot.
OpenAI Teases 'New Era' of AI In US, Deepens Ties With Government
Read more of this story at Slashdot.
Amazon Sues WA State Over Washington Post Request for Kuiper Records
Read more of this story at Slashdot.
Google Offering 'Voluntary Exit' For Employees Working on Pixel, Android
Read more of this story at Slashdot.
Oracle Faces Java Customer Revolt After 'Predatory' Pricing Changes
Read more of this story at Slashdot.
Books Written By Humans Are Getting Their Own Certification
Read more of this story at Slashdot.
SoftBank in Talks To Invest Up To $25 Billion in OpenAI
Read more of this story at Slashdot.
Has Europe's Great Hope For AI Missed Its Moment?
Read more of this story at Slashdot.
India Lauds Chinese AI Lab DeepSeek, Plans To Host Its Models on Local Servers
Read more of this story at Slashdot.
Nintendo Loses Trademark Battle With a Costa Rican Grocery Store
Read more of this story at Slashdot.
Asteroid Contains Building Blocks of Life, Say Scientists
Read more of this story at Slashdot.
Astronomers Discover 196-Foot Asteroid With 1-In-83 Chance of Hitting Earth In 2032
Read more of this story at Slashdot.
CodeSOD: Does This Spec Turn You On?
I'm a JSON curmudgeon, in that I think that its type-system, inherited from JavaScript, is bad. It's a limited vocabulary of types, and it forces developers to play odd games of convention. For example, because it lacks any sort of date type, you either have to explode your date out as a sub-dictionary (arguably, the "right" approach) or do what most people do- use an ISO formatted string as your date. The latter version requires you to attempt to parse the sting to validate the data, but validating JSON is a whole thing anyway.
But, enough about me being old and cranky. Do you know one type JSON supports? Boolean values.
Which is why this specification from today's anonymous submitter annoys me so much:
field: sw_auto_update type: string valid values: /(on)|(off)/ field: data_auto_update type: string valid values: /(on)|(off)/ field: spanning_tree_protocol type: string valid values: /(on)|(off)/Their custom validator absolutely requires the use of strings, and absolutely requires that they have these values. Sending a boolean, or worse, the string "true" causes the request to get rejected.
Our submitter doesn't explain why it's this way, but I have a strong suspicion that it's because it was originally designed to support a form submission with radio buttons. The form is long gone, but the API contract remains.
[Advertisement] Keep the plebs out of prod. Restrict NuGet feed privileges with ProGet. Learn more.Democrat Teams Up With Movie Industry To Propose Website-Blocking Law
Read more of this story at Slashdot.
AI-Assisted Works Can Get Copyright With Enough Human Creativity, Says US Copyright Office
Read more of this story at Slashdot.
NordVPN Says Its New Protocol Can Circumvent VPN Blockers
Read more of this story at Slashdot.
Atari Limited-Edition Asteroids Watches Sell Out Instantly For 45th Anniversary
Read more of this story at Slashdot.
Sony Removes PlayStation Account Requirement From 4 Single-Player Steam Games
Read more of this story at Slashdot.
Microsoft Makes DeepSeek's R1 Model Available On Azure AI and GitHub
Read more of this story at Slashdot.