My current phone has three cameras on it, two for regular use and one for selfies. If they increased the resolution of the cameras, they could easily change it to two cameras.

I could. I don't look at it as a phone so much as a foldable tablet with a screen sufficiently large as to be actually useful.

If it also happens to work well as a smartphone when folded down then that could likewise be useful.

Trouble is, it needs to be no more expensive than a phone and a tablet separately purchased in order for most potential customers to justify it. If it costs more than both combined then scant few will bother adopting it.

The design of the mouse in general needs a rethink. When mice contained an actual ball in a 3/4" or so diameter it was necessary for a particular shape in order to facilitate that ball having somewhere to go, and that somewhere ended up being under the joints where the fingers meet the palm. This was not the most efficient place to put movement detection since that part of the hand doesn't move as much as the fingertips do.

A modern mouse would work better if it had wells for the four fingers, and each finger's well was also a button, with the optical pickup to the pad/desk located under the middle finger. Or even go with a couple of optical pickups to allow for tilt. But don't have the mouse go all of the way back to the palm anymore, and keep the finger buttons as close to the surface as possible.

Was going to say, there were split-spacebar keyboards back in the day, I worked with lot of Compaq Presarios with that arrangement.

As a lefty it sucked because if the keyboard was set up for that left-side to do something like backspace on a public kiosk computer it wasn't readily changed to be usable.

For someone's own personal computer fine, do what you want. But don't expect it to become an industry standard anymore than say, Dvorak layout is.

It's interesting that you took this to intelligence and software coding when I was talking about skill and had not limited my criticism to software coding. Honestly at the time I made my post, software wasn't even on my radar, and skill only weakly correlates with intelligence.

The insidious part about using free AI is that you're training something owned by someone else to do your work. That means whomever owns that AI now has the option of replacing some aspect of your work, rendering you redundant.

For the short term, free AI empowers the unskilled masses because they can use what skilled people misguidedly trained it to do. For the long term, AI only empowers the wealthy who own it, to the harm of the unskilled and skilled alike.

some have suggested that's just because it has more or less illegally webscraped the entirety of stackoverflow and reddit, so you're really just doing a resource-intensive google search to find the right stack overflow question/answer page, without either of those sites getting any credit for it.

That's what it comes down to. When you start vibe-coding, you're no longer really coding, and you're not even really creating anymore.

You're just editing. All you're doing is code reviews and quick bug fixes...and those tend to be my least favorite parts of my job.

At least code-reviewing a junior developer, you're teaching, mentoring, instilling some new disciplines or expanding their horizons.

There's no satisfaction in doing that to a bot. Especially because the next time it codes something for you, it is going to come up with something completely different as if the 'experience' you tried to give it doesn't matter anymore.

Yeah, maybe it gets the job done...but I'm not in this to 'get the job done'. If this is what the job was or is going to become, then I'll quit, do my own coding on the side for open-source or other projects, and just make money as a substitute teacher... ...that is, if I didn't have to pay for health insurance, but America sucks in that regard and always will.

So what's the CVSS score on this vulnerability?

Again, they think they can change this crap whenever they want. Computers don't work that way. Anything that involves scheduling a future event is now a problem. If they stored it in pure UTC (just a TZ offset) or EPOC, it will be an hour off. Every single calendar event could be an hour off.

Perhaps I'm being mildly alarmist, but I don't trust entities that seem to push for their fork of an open source project to dominate the project it was derived from. Looking at the development-chart based on StarOffice derivatives, that major version-jump that Libre had was steered by Collabora. It then makes me question if they had a hand in closing down the Libre online version specifically to steer users to their own system.

We've been collecting physical movies for a long time, far longer than streaming services were a thing. For a long time my collection was predominantly Laserdisc of all things and my wife's was mostly VHS as her family had been recording off of TV for decades.

At this point DVD and Blu-Ray comprise most of our movie and TV collection but I still have well over 500 laserdiscs.

The only annoyance is physical storage. But with something like 2700 titles that isn't exactly surprising.

We got into physical media because for all intents and purposes once we have it, it's ours forever. Clearly the studios and content owners didn't like not being able to make money off of us again and again, but that's fine, we are not interested in being their ongoing revenue stream.

I have a feeling that streaming is going to backfire. People are going to become weary of trying to find a source for something and either they'll choose to go without or else they'll switch to physical media, and a lot of programming that was only on streaming will end up being essentially lost films. Lost in part because no one cares enough to try to find them, no fanbase. Sure, some will survive because they were good enough, but a lot of stuff that was entertaining but not renowned will just disappear.

because aside from the core GNU/Linux stuff, there's not a lot of C++ out there compared to TS/JS and shell (or even Python and perl and php).

C++ coding is rarely just 'raw'. usually the bulk of what you're doing is integrating multiple libraries together. How do you talk to your database? How do you create an API and/or a webpage and/or a UI? Each of these decisions requires integration that isn't published as well as the thousands of examples out there on stackoverflow for an AI to gobble up.

So internally, a team might start using AI to expand on its own code-base...but nobody is going to use AI to create a project from scratch in C++ unless speed is the #1 concern...and usually if you're heading to AI, speed of the product is not the #1 concern: speed of getting it out the door is. The AI is not going to know how to use the libraries a complex C++/C# system needs to integrate with because those are generally paid and proprietary (again, outside of GNU/Linux and Linux open source systems like gnome/gtk or kde).

we'll see within a year if AI starts getting involved in making linux desktop apps, but most windows developers will more likely use copilot for C# as Microsoft keeps training it.

I'm curious how road conditions will affect this. EVs are generally far heavier than their combustion-powered counterparts, and road conditions can play hell on cars that are heavy.

On top of that if charging infrastructure is slow to be built-out or if it's more easily damaged in conflicts, it may be hard to get drivers off of gasoline as a fuel that only requires a jug and a funnel to refuel with out in rural areas.

And it's actually more straightforward with courts. The systems for courts are regulated at the state level, even for county and municipal courts, at least in my state. That means pretty strict compliance with state-level rules and regulations and authorization by state-level officials for things like auditing and inspection. If a lower court fails to comply, that state entity can compel that lower level jurisdiction to install an entirely segregated computer network entirely air-gapped to the local entity's LAN, meaning that court employees would have to shuttle data between their local org's PC and the court PC, with the court PC connected to a court access switch and court firewalling router with a court private network link back to state resources. And historically they've been very behind the times, still using friggin' T1 lines in the 2020s, where 1.544Mb will cost as much as a 10Gb metro ethernet circuit.

State courts allow local entities to have court PCs that can be on the local org's network with connectivity back to court resources without that special air-gapped network only if the local org accepts auditing and building that connection out to specifications. Pen testing is not an unreasonable thing to do, and if it's too easy to break into the building to gain access to PCs or network equipment and too easy to get onto the court's network then there's going to be a problem.