

Aren’t all commercial plane turbine engines high bypass turbofans? (excluding turboprop)
Serious question, because I assumed that’s how they all worked, but this sounds like it is special or in spite of and it got me wondering.


Aren’t all commercial plane turbine engines high bypass turbofans? (excluding turboprop)
Serious question, because I assumed that’s how they all worked, but this sounds like it is special or in spite of and it got me wondering.


Unfortunately it has a habit of jumping around due to its asynchronous weird fuzzy search. So when typing fast you sometimes randomly launch the wrong action. It is especially inconsistent, because files are also indexed and by default it also includes web searches so the behavior is always changing.
I believe this got introduced with Windows 10 and feels just bad. Unless you are typing slowly and actually scan the results the search is doing a bad job as an application launcher like it was with Windows 7 for example.
It kinda is though. Iirc it received an interrupt it shouldn’t have received and doesn’t know how to resolve. It is not supposed to ignore it, but then the only other option is crashing at this point. Basically it continues in a dazed and confused state.
Of course the message could be clearer, but at least it also makes the message easily searchable.


Up to 355687428096000? That’s impressive!
That’s actually cool. I have to remember it next time I have to deal with html mail.


None of the tools are really made for the most trivial use cases though. Although it doesn’t take much effort to set everything up in a simple project I would probably also skip most of it. But this discussion about tiny one off projects is kinda pointless as you don’t have many of the problems to solve anyway.
I implemented a reddit frontend (kiosk mode) a while back using only vanilla JS for fun, because a previous implementation by someone else broke. There was not really a point though as it wasn’t even simpler than using the proper tools. It was just for the hell of it, but nowhere close to a “real” project.


And the simple answer is no. You can remove a layer here and there, but this is what the modern dev environment looks like.
I mean sure you can implement all that yourself and carry all the extra cognitive load, but it is not productive to even skip babel or so. There is no point, but the challenge.
Of course it is a bit more complicated to pick the right tools and you don’t have to use everything, but that’s a whole different discussion.


You always have linter steps, testing etc and a competent developer should be able to deal with all that. Of course you don’t start with all this with new students, but I don’t think that is what this post is about.


Why though? I think I am missing the point, but I don’t see the problem with having a build step in your projects. Especially for frontend it is not just JavaScript, but things like Sass/SCSS to consider etc.

Yea, no. It doesn’t work with ssh agent and it cannot read includes and other configuration options. I believe it also tries to install some components remotely which is bad enough, but causes additional issues in environments with proxies or without internet access at all. Iirc also plugins must be installed remotely to work.
In a normal professional context it just does not work and it is a hassle to deal with. It might work in a home lab, but nowhere beyond that.


Ctrl/Shift+Insert gang rise!


I was about to write the same thing. Really the object thing is the whole reason to use ORMs.
Using plain SQL is a compatibility and migration nightmare in medium and bigger sized projects. If anything using plain SQL is just bad software design at least in an OOP context.


Yea, fair point regarding the single point of failure. I guess it was one of those scenarios that should just never happen.
I am sure it won’t happen again though.
As I said it can just happen even though you have redundant systems and everything. Sometimes you don’t think about that one unlikely scenario and boom.


This happens. Recently we had a problem in production where our database grew by a factor of 10 in just a few minutes due to a replication glitch. Of course it took down the whole application as we ran out of space.
Some things just happen and all head room and monitoring cannot save you if things go seriously wrong. You cannot prepare for everything in life and IT I guess. It is part of the job.


deleted by creator


Actually I did below! You are absolutely correct.


Which actually breaks the code if you don’t have sw configured to the same width as used by the code.
If anything that proves my point.


Just copy some code over into a not properly configured vim.
People seem to forget that not everything is a fully configured development environment working locally on your laptop which attempts to fix the issues introduced by that design decision.
Ah, gotcha! Thank you for the explanation.