It's like being back in the 1700s and arguing that research into petrol is a waste of time. I absolutely do not understand this mindset.
8,196 karma · joined March 30, 2011
hn@combo.cc
It's like being back in the 1700s and arguing that research into petrol is a waste of time. I absolutely do not understand this mindset.
So technically they're not preventing access, but they nag you incessantly after you've scrolled past the fold.
Methamphetamine seems to be very effective with fewer side effects, but there's a lot of stigma and legal issues with it being one of the most controlled substances. So even if cheap it's not going to be easy or convenient to get it prescribed.
Then Vue itself became complex.
Now people recommend Svelte as an effective alternative to Vue's complexity.
Will Svelte remain simple?
It's not hard to see this constant cycle of "simplicity -> people need more -> complexity -> let's jump ship" if you're a web developer with more than a few winters. Every time there's a new simple library around the corner that makes reality so much easier to deal with, but it's mostly just hype speak and this simplicity never lasts for long.
While true, good luck living your life without dealing with a corporation.
In fact, you're a dollar sign for your next door shop as well.
Companies use social media for astroturfing and viral marketing, why not market manipulation?
Business and the economy can function without incredible amounts of wealth concentrated into the hands of a few filthy rich people.
Spoiler alert: they didn't.
Any good Switch jailbreak resources? I'm comfortable doing it, I don't know what's the latest and most effective hack these days.
I will make no guarantee to be a trustworthy person.
The velocity proposition and fantastic developer experience of writing JS in the backend and frontend and data layer is overrated and misleading. It's everything but.
Also the APIs are very simplistic, I haven't used it in the past few months when I quit my job, but I vividly recall how anything outside of the simple examples it provides were an exercise in frustration and digging into Github Issues and its source code. The whole data fetching system is so incredibly convoluted if you're doing a little more than static pages or build-time rendering. getInitialProps, getServerSideProps, getStaticProps, hooks, etc., all with their own caveats and performance considerations.
Next might be one of the better JS frameworks but it's laughably bad compared to Django, Rails, Phoenix.
* Javascript has such a minimal standard library, you will need to get one or three third-party libraries to augment its core.
* React is an excellent view library and nothing more. You will need to get one or three third-party system to turn it into a fully fledged web framework.
* Frameworks like Next.js are good enough to create a static page, but as requirements grow more complex, its limited feature-set and lack of in-depth documentation will feel like a prison.
* Dev tooling is non existent, so it's on you to get and _configure_ a linter, type checker, testing framework, bundler, etc.
Without speaking of the DOM and CSS, which are just _now_ starting to feel feature complete for most use cases.
Javascript proponents say the ability to mix and match is its strongest feature, but to me the analysis paralysis of having to stop and shop for a library that does X (and will only do X) is a total productivity killer.
Versions aren't numbers.
You can have vegetables containing potassium, sure, but it's a bit of a stretch to say that potassium deficiency is widespread, in general and supplementation of it is discouraged.
https://www.lifeextension.com/magazine/2005/9/americans-magn...