Why isn't this built into thick desktop BT clients? Is it just a little too early for it, and next year it will be? Or is there some reason I'm missing?
If you support the regime, then your most heinous crimes will be ignored. If you question the regime, then they'll find something to criminalize you, figuratively in the press if that's sufficient, or literally in the courts if need be. This has been true for all of human history, I suspect.
My two cents: the web. It's not that VB died, it's that we stopped targeting the desktop for intranet line of business apps. It all went to the web. Deployment and support of web apps is an order of magnitude easier than thick clients, maybe two orders of magnitude easier. As an industry we never looked back.
I RTFA, and this is not my experience. I just built a new gaming PC for about $900 with an AMD Radeon 6700 XT and the game runs smooth at 4K on the default high setting, about 50 fps normally. An SSD has been expected for AAA gaming for years. The game, as a game, is fine. I'm not saying you should like it, but if you don't like it then it's probably because you don't like the genre. As the article mentions, it's pretty derivative material within its genre, not exactly breaking a lot of new ground. This is fine. I have experienced no bugs whatsoever. I like the way it looks.
Different industries have different amount of willingness to endure foolishness. For at least the first 10 years, if not the first 20, any new technology is mostly foolishness. Some technology never even makes it out of that timeframe, and just disappears before then. It takes a long time to figure out which parts of a new technology are actually useful, and which parts are just foolishness. A small SaaS startup has a relatively high tolerance for foolishness. A giant bank with billions of dollars under management has close to zero tolerance.
When you say "performance/cost reasons" do you mean "just the reasons that I am familiar with and am competent to judge myself", or do you mean "all of the plethora of reasons I am clueless about, and that only an experienced actuary, accountant, or project manager from the industry has the background to judge"? I bet you're just thinking of things from your own (likely very limited) perspective. Anybody who has run even a very small business by themselves quickly finds out that a lot of the costs are hidden, subtle, and not noticed by outsiders. Can you even imagine what sorts of surprise costs are involved in running a bank?! You may think buying a cloud database from Microsoft makes total sense, and has an obvious ROI. You may also have never run a business larger than mowing your neighbors' lawns.
(I don't know you. Maybe you are the CTO of an international telecom firm. Maybe I am rude to assume your background. That doesn't change my answer, though.)
> Can [any storage that is not physically in my possession] be trusted with sensitive data?
No. You could make a case for E2E encrypted data where the storage provider does not have keys. That's pretty rare though. The point is, nobody gives a flip about your privacy. As soon as men with guns come asking for your data, any data business will hand it over without hesitation. Men with badges are only very slightly less threatening than men with guns, as everybody knows who the men with guns work for. So if you think anybody or any business is going to die on the hill of protecting your donkey porn collection, you're delusional.
I bet they have already hacked the machine. They just need legal cover to release their smooth findings. Once the judge okays it, the details will be published in 3 days. I hope.
I can't articulate this idea, because I'm not well versed enough in programming language implementation. Maybe some forth or lisp folks can help me. A programming language can be very minimal, which is great. But it does reach a certain minimum possible complexity with regard to syntax. It has to have either a toggle to switch from 'execute mode' into 'compile mode' a la forth's `:` operator, or it has to have a particular syntax difference between 'defining a function' versus 'call a function'. I'm not sure if this is true. Does lisp have such a difference, or is everything just function application all the way down? This idea is stuck in my head. Can anybody recommend a book or formal terminology for what I'm getting at here?
This makes me think. What if there was a database of conjectures. Each has an id number. The database could link to all sorts of media, scientific studies, etc. supporting or disputing each conjecture. Then you could just give the id number and folks would also get all the pro and con material they might like. Even things like "the earth is a sphere" could link to educational videos and whatnot. And even things like "political leaders who I disapprove of are in fact lizard aliens" could link to whatever material supports or disproves it. It'd be nice too if we could categorize these things: disputed, hypothetical, scientifically studied but not independently verified, multiple independent validations, technologies rely on the fact that this works, etc. I dunno why your point made me think of that.
"...with acceleration due to gravity g... A point-like unit mass slides frictionlessly over the surface under the action of gravity."
If you make up funny physics problems that don't look like the real world, then the math works out funny. What about heat, light, the motion of the larger entire system? There are a lot of forces they are just hand waving away. I think it's disingenuous to hand wave away much of the complexity of the real world and still expect your algebra problem to not be overly simplistic.
Possibly the thing that makes C be C is that there is only one C. It is the single lingua franca of "one notch up from assembly". I would argue any language that wants to be a better C has to accept the challenge of being available on any platform, existing or future, any architecture, suitable for any bare metal use case, and it has to want to be the single obvious go-to choice. That's what it means to step into the ring of "better C" candidates. A lot of languages might offer pointers, manual memory allocation, no runtime, etc. That's cool and that gets you close to the space. But if you want to be a better C, then the bar is much higher: ubiquity.
This is weird. I write a lot of technical documentation, and it often comes out reading like this. It's almost like I learned this from somewhere, but didn't realize it.
I'm in RCIA classes to convert to Catholicism. I'm skipping this Easter's big confirmation event to give it some more time. I'm chiming in to reply to this comment. Catholicism is a practical way to deal with the guilt you (should?) already feel.
Yes absolutely, it'll be 5+ years before anything like this is remotely conceivable. But I'll be working on it! When it does become possible then I'll be there immediately.
This is how I've run my 1-3 man internal corporate line of business development teams for ~20 years. I've always handled bugs first. The biggest side effect I think you'll notice is that you are much more conservative about your architecture and what new features you allow. When everything becomes a potential show-stopper as soon a bug is found, you're much less inclined to try dumb stuff.
I'd begin developing a very portable, very comfortable programming language and environment. Something akin to Pascal or Python, portable like Lua or SCUMM, less philosophical than Lisp or Smalltalk. I might not become a millionaire, but it'd be a lot of fun to start my "line of business" software development career as early as humanly possible.
If you're afraid of falling down a rabbit hole of complexity, look into Pico 8. It gives you everything you need to make a game, but also very solidly caps the level of complexity you can inflict on yourself.
https://www.lexaloffle.com/pico-8.php
You made me think "I think: [all of python] is a terrible syntax". At some point in the past, python crossed over into perl or php territory for me. The semantics, runtime, culture, support, library availability, etc. are all great. But jiminy no syntax can keep up with the decades of layers of cruft these languages accumulate. I'm starting to look at C# the same way.