now if I can just figure out how to debug a lambda function and RX stream
295 karma · joined March 10, 2023
Well.. duh?
Until AI takes over the world, this will be correct for everything. News, comments, everything.
Hibernate is an (extended) implementation of JPA. But that's because Hibernate innovated so much that they forced JPA to be better.
Leaving aside the ORM-love-hate discussion, you will do fine if you go with a JPA approach using Hibernate as the implementation. You should (theoretically) painlessly switch to another implementation.
I wonder if other Java frameworks have a different approach to serve web content without the need of servlets.
Their shady practices such as forcing exclusivity to Epic Store and suing Apple is what brought them shit all over them.
Developers are free to submit their game to Steam and release their game in any other platform. Epic handcuffs the devs to the Epic Store for a while.
> when did you ever see something critical of Steam on HN or Reddit?
Jesus are we forgetting EVERYBODY hated Steam when it got released? You know what Valve did? They fucking fixed their platform. They listened to consumer's feedback.
Now it's the best PC game store out there. That might change at some point, but today it's the best one.
I'm going to assume toasters and cars are far cheaper today than in the 70's and 80's considering all the features.
Bailout could imply government throwing a lifeguard
Shareholders will be happy the day a company produces a new product and no human ever worked on its development.
All of the profits, none of those pesky workers demanding silly things such as payments and OSHA protections.
Hopefully they aren't lying.
But that single DB is just a piece of the business puzzle. Networking, web applications, even backups. That's hard to migrate (And hard here means it will take massive effort and time)
Good teams have plans in case they need to migrate. But I think not all teams are prepared for such scenario.
The biggest challenge when you have on-premise infrastructure is battling managers to get an additional server.
I have seen managers laughing at my team leader when he asked for a server to do some QA. We needed the server to perform some tests for a critical product. They even had the audacity to say "Hey Manager Bob, how long have you asked for a server?" Manager Bob answered "It's been month's now"
Granted I think that's an extreme example but I don't doubt it was a common occurrence back in the day. Now I also have worked on enterprises where asking fora server (Or RAM increment in a given server) is as easy as submitting a ticket and waiting for a FEW DAYS.
Cloud is more expense on the long run, but it sure gives you agility to do things.
https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
So I don't HAVE TO pay the license every year! That's good to know if I ever have to reduce my bills.
At no cost and no sacrifice.
Personally, I'm not going to sacrifice my car or my A/C although I know it will help reduce CO2 emissions.
First, that Spring it's bloated. Spring now has a wide extension of modules that you may or may not need. Most of those modules won't even be added in your classpath unless specified in your pom.xml or build.gradle file. Very simple projects won't need the vast majority of the full Spring power.
Second, that a Spring project takes too much time to launch the web app (Compared against other frameworks doing the same task). Part of the reason it takes too much time to start comes from how the engine inflates the beans and injects it. On that same topic, other frameworks such as Micronaut are more lightweight because they don't bloat the framework as much as spring, thus the launch time is shorter. Also take into account that Java developers adore complexity in code structure so that also affects launch time.
Are you going to regret going with Spring? No, there is a lot of support from the community, if you have any issue you will find help in reddit and stackoverflow. It's a really mature framework.
However it's not the only option. There are other frameworks that could be a better choice for your use cases.
That's true in specialized career paths. A Doctor, a pharmacist and lawyers are good examples. Don't ditch the degree requirement for those.
However I've seen "offices" jobs where they only require people that can read, write, have basic MS Office skills and specially FOLLOW INSTRUCTIONS. You can learn that in high school.
But companies require Degrees for those jobs and it's the most idiotic thing I can think because:
a) Companies are downsizing the pool of potential candidates and, b) People with degrees (Some of them at least) will feel that job is not fulfilling. They will leave for better opportunities.
For those jobs, just learning on the fly will suffice.
Or is schizophrenia a spectrum very much alike as autism?
Fewer colleges mean:
1) People out of jobs. Teachers will lose their main income and the remaining colleges will have no incentive to increase their payroll because where are they gonna go?
2) Getting into a college will be even more competitive. As companies will still look for people with degrees, colleges can charge even more and candidates to study there will have less choices.
This will only change when NOT studying at a college has no impact in your future income. Or the impact is lesser than today.
You would if you had nothing to do other than walking into a fertilizer store. Very small chance of happening that to you, but I do like going into stores and see what they sell even if I don't need anything in there for me.
I might learn something.
That's a failure on the developer's communication. If everyday you find a new challenge, then everyday you must communicate that new challenge.
Code changes/features is not one to one. It's a bunch of changes to provide one feature. And remember we can at best estimate the time it will take us. Estimates are often wrong because of things we didn't know that we didn't know.
There won't be an agreement here because it's just semantics. The opposite sounds very true as well. Let's reverse it.
"The thousand-songs-in-your-pocket sales pitch was more than a feature-- it was a lifestyle/concept."
It sounds.... exactly the same to me. Both words (lifestyle vs feature) have the exact same impact if it's the final word.
> you're not really paid for agonizing over eloquent or great code, but just code that "gets the job done".
Somebody might interpret this statement as if nobody (in their context) should worry about writing good code. If you're writing good or bad code it doesn't matter as long as it works. Package and ship it and call it a day.
But the author addresses this:
> It's not even about good work. This is also a given. That's the default expectation, it's part of the package. The cake will be good.
Then I'd say that you're paid for "good code that gets the job done".
People still ping me frequently for a "quick chat" which is rarely quick, tho.
That's one problem but not the most crucial one. There will be a bunch of people complaining that they do all the work while the freeloaders have it easy.
We can see that today as people don't want universal health care or social safety nets because these people feel the freeloaders are taking advantage of them.