It seems endemic, especially everywhere that's not a product company. I think it was mythical man month (maybe earlier) that pointed out the 90% of the cost of software is in maintenance, yet 50 years on this cost isn't accounted for in project planning.
Consultancies are by far the worst, a project is done and everyone moves on, yet the clients still expect quick fixes and the occasional added feature but there's no one familiar with the code base.
Developers don't help either, a lot move from green field to green field like locusts and never learn the lessons of maintaining something, so they make the same mistakes over and over again.
I really like the way kakoune (https://github.com/mawww/kakoune) handles it, the editor doesn't have any scripting as such, it has an "API" in the form of pipes and environment variables that can be used by shell scripts or tools written in any language. Unix is the IDE.
I just could never get my head around the key bindings with kak.
But that goes back to the original point they made, everything outside of the actual text editing and you're in EMACS land with all of it's controls. Even with something as complete as spacemacs, the default landing page when you open it has different key bindings.
> Edit: Oh! I almost forgot, there are people who built their house next to a NASCAR track! WHO thinks that is a good idea?
Depends on how often it's used I guess. At times I've lived a couple of blocks from a formula 1 track and right on a hairpin bend of an IndyCar track. Both were held once a year so even though I don't like car racing it was a feature not a problem.
I find 90% of the complication in large enterprise projects come from the developers trying to write too much architecture and not enough simple, boring, imperative code. At the moment I'm staring at a validation framework and 6 layers of validator inheritance who's job it is to verify that one number is bigger than another one. That's just for one tiny part of the overall system, nearly everything has to be in some inheritance hierarchy or pattern to minimize duplication or even worse, abstracted into an internal library that makes the entire organisation tightly coupled. God forbid you declare more than simple data class per file. We have tens of thousands of lines of code just to extract a few values from a csv file, tens of thousands more to write xml documents all because someone had to prove how clever they were.
Once you take away all these unnecessary complications you quickly find a lot of "large enterprise software" could be a few scripts dropped into a cgi-bin directory, some could even be a shell script + cron. I think we'd be better off with this as the starting point for all enterprise projects and should not become a "real project" until they past a point of complexity where they really deserve to be.
I'll take small stand alone spaghetti scripts over bloated architectures any day. At least they can be refactored without taking the whole system, all it's libraries and half the enterprise into account.
> Edge lets you turn that off - on the New Tab page, click on the cog symbol (Customize) and you can choose from New Tab page display settings: Top Sites & My Feed, Top Sites, or Blank Page.
I shouldn't have to turn off whatever spam they build into a paid for product. It should also be in the browser settings, not a confusingly placed and easy to miss hieroglyph. For me I don't even get those options, it's just a toggle to turn the news feed on or off, off leaves you with just a search bar, and bing is the only option builtin.
The store couldn't have been great for enterprises too, replacing custom scripts, click once etc but it's gimped in a few critical ways, like cloud reliance and no way to push upgrades.
I grew up on the Gold Coast and definitely enjoyed that birthright, playing in the ocean shallows from before I could walk, doing nippers at age 6, etc, but I believe the Queensland standard has also dropped to 50m. I don't think many public schools there have pools even now though, it was almost all private ones when I was a kid. A big differentiator in Qld was the huge number of backyard pools, but they seem to be disappearing as Qld catches up population wise with the southern states, not to mention costs with recent droughts.
Watching my nephews that nature of their swimming seems to be a bit different, for me we were riding or bikes to pools/beaches by ourselves from the age of about 9, they live in Brisbanes suburbia and have to be driven to a pool/beach and then supervised. They're largely left to their own merits once they get there, but it's more of a family thing than a friends thing and they don't have to learn there own dispute resolution and the like, nor do they get to decide when to go and when to leave.
> In older times being a child often meant forced labor and exposure to brutal or shocking parts of life before you were ready.
That was also mostly an aberration (for non-slaves) and mostly during the industrial revolution. Peaceful childhoods certainly existed before then if you look at tribal societies and the way they gradually give kids more and more real responsibility.
In Australia at least this is an area we are getting worse at (https://lsv.com.au/research/water-competency-of-victorian-ch...). 3 out of 5 fail the current standard of swimming continuously for 50 meters at the end of primary school. The standard has dropped too, ~25 years ago when I was tested the standard was 200 meters and most of the "training" happened in unstructured time.
A simple php endpoint is something any web developer can understand. The more frameworks/libraries/patterns/abstractions you throw in the less likely it is they will understand it. Especially years later when the framework is inevitably out of date, good luck convincing why they need to spend money upgrading a framework every year.
> hey can we put Google maps in here?
Has this changed recently? Last I checked you would just drop a script tag into the page, who needs a library for that? Edit - I checked (https://developers.google.com/maps/documentation/embed/guide), how does a framework make a copy/paste job any simpler?
> "we need to integrate with stripe payments"
I'm not familiar with stripe, but don't you just give it a return url? I don't see how a framework would help at all here.
> you'll need to stay 100% up to date on all security issues/approaches/classes of vulnerability to make sure your custom system is secure.
This is harder with a framework, it's one more thing to keep updated. The less libraries the less vulnerabilities.
Did you consider that up to a certain point any framework, be it home grown or commonly used, makes things more complicated?
Simple cgi endpoints and static files for any css/js should be our starting point and any web developer should understand them. When the problem becomes bigger and more complex is when we should start looking at frameworks.
> According to the official release notes, this vulnerability involves a memory mismanagement bug in a part of Chrome called FileReader. That’s a programming tool that makes it easy for web developers to pop up menus and dialogs asking you to choose from a list of local files, for example when you want to pick a file to upload or an attachment to add to your webmail.
It sounds like the bug occurs interacting with external code, win32 or equivalent. Even if chrome were written in a "safe" language this section would likely be in unsafe block.
This is what CDNs are designed for, the allow a few companies to get a monopoly on your browsing data. This is why I prefer uMatrix, it blocks all third party requests, a lot of stuff breaks but it breaks because their tracking you.
I've seen this time and time again and every time the sum "linux" bug ends up affecting some browser/OS combination that is supported. It's not breaking because it's linux, it's breaking because there's a bug and sooner or later it will rear it's head elsewhere.
Consultancies are by far the worst, a project is done and everyone moves on, yet the clients still expect quick fixes and the occasional added feature but there's no one familiar with the code base.
Developers don't help either, a lot move from green field to green field like locusts and never learn the lessons of maintaining something, so they make the same mistakes over and over again.