And as other commenters have pointed out, lots of budget phones and hardware jam ads all over the place.
Premium hardware too (hello Smart TVs)
215 karma · joined May 9, 2018
And as other commenters have pointed out, lots of budget phones and hardware jam ads all over the place.
Premium hardware too (hello Smart TVs)
Chrome is the new IE and Google is the new Microsoft. They make up their own standards on a whim, which thanks to market dominance everyone is forced to follow. They collect user data without permission. They waste computer resources. They push people towards other Google products in an anti competitive way.
Mozilla has made some dumb mistakes here and there but it pales in comparison to the very serious threat that Chrome, and Chromium in general has to the free web and to users.
It's worth noting that the complaints below have nothing to do with the article, which shows a pretty promising tech, and are just bagging out FF because just as you said, that's what happens on HN.
That being said eventually you end up with both the Gnome and KDE libraries anyway - plus a handful of Electron apps are unavoidable today.
Secondly, and I don't mean to disrespect you in any way, but if you're self-taught, and your prior experience is one man jobs working on small sites then I wouldn't expect the quality of your code to be great. I would be wondering how much time it would take to ensure whatever you build is really readable, documented, fully tested, maintainable, in line with the company's current tech stack, performant and scalable.
The benefits of working at a large company is that they have products that run on massive code bases that are, for the most part, REALLY STABLE. They move slowly, but they also move surely. New code won't be scrappy and volatile. Old code can stagnate, but it's because it hasn't broken in years. All of these things are learning opportunities you can take with you even if you strike out to start/work at a startup.
As for the massive codebase, try to specialise in an area and own it. Take lots of tickets around that module / namespace / whatever and you'll end up in a niche with lots of ideas about how to modernise, optimise or otherwise improve that code base, as well as teach you a lot about the companies coding standards and practices when you're ready to move horizontally into other parts of the code base. You will become trusted as an expert in that area and valued by your colleagues.
Large code bases are a reality in programming. All of your smaller app and websites are built on top of the massive code bases of your favourite JS frameworks, web servers and web browsers, which are built in operating systems that also have massive code bases. All of those code bases, by the way, started out small as well, and grew to meet bigger and more demanding requirements.
You are kneecapping your potential if you decide to stop at the software development equivalent of barre chords.
It's already impossible for a lot of people to host their own web server from their home, to own the media they purchase without it potentially being erased by the vendor at a whim, to opt out of social media without a massive social (and professional) hit and computer power is being wasted on shitty electron apps and built-in OS adware.
Oh, on the subject of computer power being wasted, on a global scale it's being wasted on crypto, another attempt by a bunch of elitist executives to invent something that allows them to invent a new financial system in which they're still on top, but allows them to more easily commit tax evasion and money laundering.
All of our tech advances have largely been from massive companies trying to add scarcity to a system we invented that absolutely doesn't need it. Can't copy a MP3, can't copy an EXE, and now, you can't copy a JPG.
Yes, we do in fact have to participate in these dumbarse discussions. The choice to simply walk away from these things, particularly AS a tech worker, is bullshit artistry.
Remember to right click and save.
Generally speaking once a game developer gets it working on Ubuntu the Arch wiki guys will happily figure out the rest on their own.
But yes, the downside is the lack of smooth integrations. When I tried Jellyfin about a year ago they did not quite have Chromecast support nailed down, however as of now they've got a fully functional Android app and proper Chromecast integration.
Just because the Microsoft Store didn't pan out a few years ago doesn't mean they won't try again.
So they were doing that anyway.
edit: or thai, or arabic
I always liked this.
While Asian countries proudly and unabashedly pursue technological advancement and innovation western policitians are still pretending that our economy is dependent entirely on guys mining coal with a pickaxe.
You can see the Western fall of technology not only in AI but in renewables as well.
At what point did people who browse a site called "Hacker News" start believing in Security through Obscurity?
Nor has he moved beyond a Java 6 mindset considering the things he complains about in terms of modularity, verbosity and even strict type checking.
The fact that he thinks that the IDE race is between Eclipse and Netbeans is telling.
As far as boilerplate and unneeded code goes, he is correct. Spring, Hibernate and Spring Boot removes code, and results in some arcane problems that you shouldn't need to learn about. Now, let's discuss the React ecosystem: explain to me the purity of intent behind an application that requires: - action classes/files - reducer classes/files - possibly route classes/files - a "store" - a component to set a variable, complete with the half dozen packages required to enable this behaviour. Not everyone has to do this, but when creating a React application with the kind of scope that a Java application often requires, this is an inevitably, and a LOT of work for a supposedly simple task. If there is an error, you are similarly going through a stack trace of weird abstract classes, except they are in a bundle file which is equally impossible to parse.
/r/civbattleroyale is generally a lot more interesting given a lot of civs are selected specifically to try to play to their terrain strengths.