![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
I don’t understand how their decision 3 years ago “worked” and that’s why they’re changing the license again.
I don’t understand how their decision 3 years ago “worked” and that’s why they’re changing the license again.
I remember reading that the banks who loaned him the money haven’t been able to sell off the debt.
* { display: flex; }
What’s their ticker? I looked up BSOD but that’s not it…
YOUR ACCOUNT HAS BEEN SUSPENDED BECAUSE YOU DARED TO COMMENT WITHOUT PROVIDING THE EXACT SOLUTION FOR OP’s PROBLEM (shame on you)
Wait what was the solution?
Found a solution, thanks everyone!
But how’s the java support? If it’s better than vs code then it might be worth something.
I think basic or even complex stuff is fine in vanilla js.
The problems show up as you scale the team and code base. You can do a large project in vanilla js but you’re going to have to solve a lot of the same problems frameworks/libraries have already solved. Maybe it’s worth it, maybe it’s not.
I do microclouds in the service.
Yeah but it’s just going to get better at magicking. Soon all us wizards will be out of a job…
Not saying anything about good or bad, but trunk-based development doesn’t work when the business requires you to have multiple releases under development concurrently.
Good one, I hope others can learn from my mistakes
SQL-99 called and wants it’s joke back
I know of 2 projects that wanted to migrate from Oracle to Postgres, one of which was successful. Both migrations were driven by cost savings–Oracle can get exceedingly expensive.
In both cases there was up front analysis of Oracle specific features being used. A lot of that could be rewritten into standard SQL but some required code logic changes to compensate. Vendor lock-in is insidious and will show up in native queries, triggers, functions that use Oracle packages, etc.
Changing a project’s underlying database is rare, but not as rare as it used to be.
These days this reads as some kind of managerial feel-good comic.
Take your example of adding a field to an entity. Just because you’ve made that code change doesn’t mean other code should be using it. Who should be using it and how is determined by the business rules.
Also your interest in ensuring it is “properly” used is impossible to enforce. What’s considered proper even for existing code can change over time.
Hmm I think you’re looking for a technical solution to a non-technical problem.
Click bait. From an article last year:
These effects may be troublesome, but they are short-lived; re-ionization occurs as soon as the sun comes up again.
https://earthsky.org/todays-image/spacex-launch-punches-a-hole-in-the-ionosphere-red-blob/