The TI-85 also didn't have a lot of the built-in statistical functions that the TI-83 had.
I also was the one person with a TI-85 in a school of 83s. But by the time I took the statistics class I knew enough BASIC to write my own programs to replicate the functionality that was missing.
The average person is slightly more female than male and has 2.1 children, but they do benefit from defense contracts since it makes up a small percentage of their salary.
'readSync' does two different things - tells the OS we want to read some data and then waits for the data to be ready.
In a good API design, you should exposed functions that each do one thing and can easily be composed together. The 'readSync' function doesn't meet that requirement, so it's arguably not necessary - it would be better to expose two separate functions.
This was not a big issue when computers only had a single processor or if the OS relied on cooperative multi-threading to perform I/O. But these days the OS and disk can both run in parallel to your program so the requirement to block when you read is a design wart we shouldn't have to live with.
The application in question is frozen for that period though, that's the wait they're referring to.
Even websites had this problem with freezing the browser in the early AJAX days, when people would do a synchronous XMLHttpRequest without understanding it.
he was referring to fs.readSync (node) which has also has fs.read, which is async. there is also no parallelism in node.
i don't see it as very useful or elegant to integrate any form for parallelism or concurrency into every imaginable api. depends on context of course. but generalized, just no. if a kind of io takes a microsecond, why bother.
And then it will be just another war crime committed daily conflicts, and nothing will happen because there is no world police ?
Ask Ukrainians, Lebanese, Gazaoui, Somalilanders, or even Iranians for that matters - that may not make a big difference to today...
What I would love to see is a local government suing an arms producer for the efficacy of their weapons. (Or even funnier, the owner of a home destroyed by a drone, suiving the GPS company.)
We all know that the only things people in suits are really afraid of, more than hell, is a bad Q4 report and an expensive lawsuit.
The GDPR is vague and unworkable as written. It fundamentally restricts all data processing with a few, vague exceptions.
What is data processing essential for the services being provided? Many publishers assumed that getting paid was an essential part of providing a service, and it was not until 3 months before the implementation deadline that the committee clarified that getting paid is not included when you are being paid by a third party.
How are you to know whether or not the user is an EU citizen (and thus subject to the GDPR)? Is making that determination a service essential for providing your service? The answers apparently were "You don't" and "No", which would effectively make companies assume that the GDPR applies to everyone on the planet.
The GDPR also is fundamentally opposed to how things currently work in the internet, making almost all advertising on the web illegal overnight. It was too big of a change to happen at once, so it effectively only loosely enforced in practice.
I like the idea of the GDPR, but the implementation sucks.
> The GDPR is vague and unworkable as written. It fundamentally restricts all data processing with a few, vague exceptions.
What utterutter FUD
You are free to collect as much personal data as you want, PROVIDING you have my explicit opt-in informed consent to do so.
What about this is difficult to understand?
> How are you to know whether or not the user is an EU citizen (and thus subject to the GDPR)?
The GDPR provides _basic_ data safety and consumer protection. If you aren't protecting users private data regardless of where they live in line with GDPR principles (such as collecting it fairly, and not selling it to randoms) then you are playing fast and loose with your users private, sensitive data. In which case you need to _seriously_ consider if what you are doing is ethical.
> The GDPR also is fundamentally opposed to how things currently work in the internet, making almost all advertising on the web illegal overnight.
Utter Bullshit!
You are free to advertise as much as you like! But if you want to track me with your advertising (hello scummy adtech industry) then you need my explicit informed consent to do so. And so you should!
Again, what about this is difficult to understand?
> If you aren't protecting users private data regardless of where they live in line with GDPR principles (such as collecting it fairly, and not selling it to randoms) then you are playing fast and loose with your users private, sensitive data.
It's interesting and revealing when someone responds to a law that says "You're not allowed to abuse users in countries X, Y, and Z" with "How can I figure out who's in the other countries, so I can abuse them?" instead of "I'll just stop abusing everyone, and then I don't even need to worry about where anyone is."
Whenever you find yourself asking "how do I toe as close to the 'illegal' line as I can without technically going over it?" I think it's time to ask yourself some pretty hard questions.
Agreed. I've been on the market for a new car to replace my aging Prius for for the past three years. All of my top choices are "not sold in the US".
I don't need a giant fricken SUV to go to work. I don't need 400 miles of range (the other car does that when it's needed). But I do need room to fit the kids and their stuff in the car. There's literally nothing sold in the USA that's suitable for this use case.
FYI: Gemini Cli is used internally at Google. It's actually more popular than Antigravity. Google uses MCP services internally for code search (since everything is in a mono-repo you don't want to waste time grepping billions of files), accessing docs and bugs, and also accessing project specific RAG databases for expertise grounding.
Have you tried it? It's like working with an idiot savant. It's absolutely brilliant, but goes off the rails constantly, spewing out CoT when it shouldn't be, getting into weird loops, spewing gibberish or repeated phrases. But when it does actually work, it's brilliant. But the issues make it unusable for dev at any level - and completely untrustworthy. Contrasted with CC or Codex CLI it's night and day. The latter two are incredibly reliable, rock solid, and crazy productive, and becoming exponentially more so by the week.
I also was the one person with a TI-85 in a school of 83s. But by the time I took the statistics class I knew enough BASIC to write my own programs to replicate the functionality that was missing.
reply