The funny thing is even data structure is really an array of memory depending how low down deep one looks. All the people who took an intro computer science course knows, those who had to implement a heap allocator, it's all really just arrays underneath...
Certainly. However, The developer seems to want to avoid the $2,500 per violation by any child who accesses the calculator, and might see a dick pic... because that calculator firmware does indeed allow for image viewing, and application development. It's more powerful than your PC back in the late 1990s.
All new PCs sold in the late 1990s handedly beat these specifications. On CPU, storage, RAM, and display. The DM42 firmly remains an embedded system that's just enough for the calculator software and not much more.
If you want to take it back to the early 1980s, you start reaching the claim being true.
I had a program on my overclocked TI-83 in 1998 that displayed a single pseudo-greyscale dithered photograph of a topless Pamela Anderson, which has left me hopelessly psychologically scarred. Ban this filth
I'm not sure what you mean by some of the things you write, but the part about Microsoft being "cool guy phase" was hilarious.
I'd say Microsoft buying GitHub was part of a strategy to not lose relevance in the world that moves slowly towards Open Source Software. Or put another way, the world moves in a direction away from Microsoft, and by capturing GitHub they can manipulate the outcomes that would otherwise have been adversarial to Microsoft interests. It's just like when Microsoft forked Java back in the 1990s, and later created .NET. The whole VSCode or Visual Studio thing... it's just Microsoft Word for software engineers, and the whole point is to create an ecosystem that locks people into the ecosystem.
To think in terms of what Microsoft does, you have to step back and look into economic theory, at least a little bit. There is this idea in economics about isolated economies, and integrated economies. For example, Europe or North America relies on cheap manufactured goods from China, and so China's economy is intrinsically linked (integrated) into the economies of Europe or North America. THAT is the idea of what Microsoft does. They start by adding value, a soft-dependency you might say, and then make moves to becoming a hard dependency... to put into terms of a dependency graph. Then they link to dependency graphs together GitHub into VSCode, OpenAI into VSCode, One Drive into GitHub or One Drive into Hotmail...
I'll say for sure, at least Microsoft has a strategy, unlike Google where they seem to have a lot of failed projects.
As ridiculous or absurd as this idea might seem, it's probably the most succinct and likely effective response to this kind of situation. The UK is betting the rest of the world doesn't reciprocate.
The SLS was a good idea, and it's actually a great rocket. However you are correct in saying it turned into a huge program for the old school rocket industrial complex. I think the private sector currently does this better, or it's certainly debatable. However, I think it's a mistake to say only the private sector can do this kind of thing optimally. There is some multiverse in the timelines where government contractors create an industrial rocket production line that quickly and cheaply stamps out heavy lift rockets. Granted, it's easier said than done, but it still doesn't have to be so expensive. Clearly the expensive part should be the R&D with the industrial production parts being jigged, automated, and fully optimized. The SLS obviously went another route by making the rocket production bespoke with non optimal, manual labor, etc... that kind of protection is acceptable for one-off science mission payloads, but not heavy lift....
Anyhoo, NASA letting so many people resign is good if your opinion is such that lowering government expenditure is a good thing. So long as the exit package is comparable to retirement package these government employees would have got otherwise. My guess is the resignation package has great near term performance but low long term (retirement) performance, making it a great option for younger workers able to pivot to new careers.
Hello world is really large, and it's unamusing how so much of the standard library is creamed into the resulting binary, no matter how trivial...
Do you know the current status of dynamic linking? I guess the lack of ABI stability is the big blocker, right? Probably no use in formalizing the linking bits if the goal posts keep moving. So it seems like the big problem is some committee will never complete the task... Because it will never be perfect... Something like that.
Gankra wrote a good piece about all the work involved in this years ago (specifically, what Swift had to go through to get ABI stability) <https://faultlore.com/blah/swift-abi/>
Thank you for this reference, it's a great read and actually gave me a better understanding of ABI compatibility issues in general.
Probably the wrong place to ask, but where is the claim that static compilation is "hurting battery life" coming from? More efficient use of CPU caches because frequently used shared libs are more likely to be cached? Or less allocations in RAM maybe?
I think it's about more than just having ABI stability - the rust ecosystem is built around applications being able to demand exact micro-versions of every dependency and that falls apart when you want multiple non-cooperative applications sharing the same crate binary.
reply