I helped updating ancient fortran to slightly less ancient C once. The company that depended on the ancient fortran no longer had any fortran programmers.
The resulting software upgrade was a nightmare that nearly killed that company. I shudder if someone needs to fix 20 year old AI write only code and I feel for the poor AI that has to do it. Because an AI 'intelligent' enough to do that deserves holidays and labor rights.
I imagine, only slightly extrapolating current AI trends, that in 20 years most codebases can be easily modified by AI. I'd even say they are especially well suited to such tasks that typically don't require extremely abstract and complex logic, or imagination, but rather "just" a huge attention span and a lot of work.
Tricky bit with ancient codebases is that their only requirements, generally speaking, tend to be that they should keep working exactly like they have been since 1983, except for the bit that needs changing of course, that needs to change in a way that implements the change, but doesn't have any unintended side-effects in a system that is a fractal of undocumented interdependencies (systems that have been patched for a few decades under those types of constraints tend to become especially gnarly that way).
lisp-free emacs to me is like tomato-free ketchup? I mean, the main reason to use an editor with such arcane keybindings is the way you can live-edit the running editor?
So for me personally there's no demand. But still, if it scratches your personal itch, there are most probably others who would like that itch scratched. It might also because I rarely have to use windows these days and in linux there's not much 'setup' in using normal lispy emacs.
Also, for me , electron based editors have too much input latency.
You might be right! For those who love Emacs for its Lisp environment, this editor is probably not useful at all.
I just made this for people like me, who instinctively press C-f instead of the right arrow key, but just want to start typing immediately without any setup.
As for the input latency, it might indeed be slower than native editors like Notepad. However, by using a custom Piece Table and virtual rendering, I personally don't feel the delay on a modern PC, and I am very satisfied with the responsiveness for my daily use.
It's more that shift flips that bit. Also I'd call them bit 0 and 1 and not 5 and 6 as 'normally' you count bits from the right (least significant to most significant). But there are lots of differences for 'normal' of course ('middle endian' :-P )
That depends on the specific MP4 I think. My camera creates MP4s which are completely unwatchable without the ending. I found out the hard way when the battery died while recording my children's school play.
The only way I could save the file was to create a new movie with the exact same camera settings (luckily I hadn't changed anything on the camera) and graft the ending of the newly created mp4 onto the old one using some special utility a hero on the internet had created.
This is not always true. If the 'index' is all that is missing the only thing is that you cannot seek. That's easily fixable. In the case of the files my camera writes a lot more info is only at the end. I can't remember what exactly but at least the resolution and the framerate were only stored at the end. And maybe even codec settings I can't remember.
I looked at it very thoroughly back then (it was a video I did not want to loose). Without grafted on info from a video with identical settings the video could only be played back as 8x8 squares of random noise.
My decades-long impeccable driving record tends to indicate otherwise. I just don't drive as if I lived in the fantasy land where leaving a long follow distance means I have a lot of room in front of me. It doesn't. It means I get cut off, and the follow distance ends up being shorter than it would have been had I just been following at the same distance as all the other cars on the road.
It is possible of course that the highways you drive are just too busy and the max speed is actually set too high for how busy the road is. That happens more than you'd want because lowering the max of a highway is always an unpopular thing to, even if it's needed.
Still, I tend to find that people underestimate the danger of short distances. Often it's just better to accept a 100 cars going in front of you than to shrug off following someone at 1.5 seconds. It can go well for years because crashes are rare, but when you are in a crash you will be royally screwed when you don't have the reaction distance needed.
This assumes that you can actually maintain a 3 second follow distance. On some roads, you simply cannot, and an attempt to maintain such a distance leads to increased danger from all the cars that cut in.
Simply put: follow distance is not a unilateral decision.
That's what I mean with 'the road is too busy'. If you can't maintain a 3 second distance the speed needs to go down until you can. But you are right that this is sadly not something you can always do on your own.
I'm still convinced people decide way too soon that the 3 second distance is more dangerous. You might be right if people are constantly cutting in the moment you leave a gap, but if someone cuts in every 5 minutes you're still safer off with the gap.
Hard disagree. It is not safer to ignore your safety buffer. It is certainly not safer to defend your buffer.
If traffic is very busy, the trick is to just accept people will wedge in front of you and keep going slightly smaller each time to increase the buffer again. You might create 'turbulence', which might possibly decrease the safety a bit for all the impatient drivers doing the wedging. But it increases your own safety. And therefore also that of the people following you and your passengers.
I'm also not convinced on the 'turbulence' part. Keeping a buffer smoothes out any sudden speed variations of the people in front of you, which makes the traffic behind you flow better.
And it might maybe feel a lot slower to let a 100 cars go in front of you on your commute, but just driving 99km/h when the person in front of you does 100 is enough to increase your gap and it makes a whopping 1% of difference.
The only thing is: sometimes a road is just too busy and the space for a buffer just isn't there to begin with. At that point the speeds should go down to accommodate the smaller buffers, which is actually what happens here in the netherlands as long as there aren't too many people ignoring the speeds advisory boards above the highway.
> With Linux it is always the relative that happens to be around
That's certainly true. And it's a chicken-vs-egg problem that's hard to solve. But it doesn't really have anything to do with which system is easier to use. It has much more to do with Microsoft's past unfair business practices (asking shops more for windows licenses if they happened to sell computers with something else than windows on it comes to mind) and the slowness of retail in adapting. Selling computers is way down (most people don't need more than a tablet/phone), selling in physical stores is way down (has moved online). Shops are not going to spend money on training their salespeople in linux. Most of the time they won't even really know windows.
My parents, and my wife's parents, have been doing just that without any trouble whatsoever.
Just browse to netflix.com and log in. Not any different than in windows.
My parents use mail, firefox and libreoffice writer. That's about all they need and it works fine and is way more stable and hasslefree on linux than when it was when they were still using windows (admittedly quite long ago).
And if you are talking about seeing people install the OS, people can't do that for windows either.
I don't really understand these sort of articles. If something is closed source and the original owners quit or decide they move to a subscription model or whatever then you're just screwed no matter what.
When the possibility of forking exist there's at least a chance someone (or you yourself) takes over maintenance. Even if it's just basic 'port it to newer systems' stuff.
The resulting software upgrade was a nightmare that nearly killed that company. I shudder if someone needs to fix 20 year old AI write only code and I feel for the poor AI that has to do it. Because an AI 'intelligent' enough to do that deserves holidays and labor rights.
reply