This is amazing! I always get questions from new developers or students similar to "I want to do/be X, how do I start?" and now I can point them to this. Thank you for this.
Developer Roadmaps
121–130 of 139 posts
Re: Developer Roadmaps
#122Earlier quoted context omitted.
If they don't have any respect for their users I guess.
Only if by users you mean people living in the terminal. Yeah, those people hate GUIs, compositing desktops and anything more than monospaced text. Just whisper "Emoji" in their ear and witness the Wrath of Khan unleashed. I would say exactly the opposite, not using web-tech for GUIs is disrespecting the users, because the end result is an ugly app with a lot of missing features (gif/image/emoji support for example).…
Because they offer a gratis plugin eco-system over the competition that outweighs the disadvantage of running a memory hungry application.
Other than VSCode, my computers are free from Electron virus.
Re: Developer Roadmaps
#123Earlier quoted context omitted.
A tablet with keyboard is a desktop. A laptop with wireless connectivity is a desktop. Anything with a pluggable keyboard and screen is a desktop. Something that many fail to grasp.
What's your point? Just like "front end development" implies "web development" to most people, "desktop development" implies "development that is not web, Android, or iOS".
To people that don't know better.
Re: Developer Roadmaps
#124Earlier quoted context omitted.
What's your point? Just like "front end development" implies "web development" to most people, "desktop development" implies "development that is not web, Android, or iOS".
To people that don't know better.
Are you really saying that there are people posting to HN that don’t know “desktop applications” don’t include applications running on laptops?
Re: Developer Roadmaps
#125Earlier quoted context omitted.
When people in the modern era say “front end developer” that basically implies web. Most people in common nomenclature don’t call iOS and Android developers “front end developers”. They are referred to as “mobile developers”.
Plenty of digital agencies do frontend work across multiple delivery platform formats
They also do SEO and WordPress sites. And many of the front end devs also do back end or devops, and vice versa. "Front end" isn't a synonym for an agency employee, it's just one role that may be needed at such an agency.
Re: Developer Roadmaps
#126Earlier quoted context omitted.
Frontend roadmap completly ignores everything that isn't a Web browser. So no Qt, wxWidgets, Android, iOS, WPF, Forms, UWP, WinUI, GNOME, KDE, ...
Except Android/iOS, everything you listed is dead or dying. No sane person would pick anything but Electron for a desktop app today, unless you are in a particularly high performance domain (CAD/Graphics/Video/...)
> No sane person would pick anything but Electron for a desktop app today, unless you are in a particularly high performance domain (CAD/Graphics/Video/...)
People who don't hate their users or who don't hate the environment might.
Electron apps use lots of CPU, lots of RAM and lots of energy. I get that they're easy for web devs to make and I've made them before but I'd fight tooth and nail against launching one at scale (like Slack did, for example).
Re: Developer Roadmaps
#127Earlier quoted context omitted.
Except Android/iOS, everything you listed is dead or dying. No sane person would pick anything but Electron for a desktop app today, unless you are in a particularly high performance domain (CAD/Graphics/Video/...)
> No sane person would pick anything but Electron for a desktop app today, unless you are in a particularly high performance domain (CAD/Graphics/Video/...) People who don't hate their users or who don't hate the environment might. Electron apps use lots of CPU, lots of RAM and lots of energy. I get that they're easy for web devs to make and I've made them before but I'd fight tooth and nail against launching one at…
Well, if you make the energy argument, theres a lot more to cut then.
How about high resolution displays? And bit depths? We can perfectly work on a 1024x768x256 colors screen. Imagine how much CPU/GPU cycles that would save.
Re: Developer Roadmaps
#128Maybe not a developer roadmap per se, but I refer to this data science roadmap[1] from time to time. It isn't a definitive statement on what makes a data scientist, but it does help me pick the next concept to learn and make knowledge gaps more obvious.
[1] - http://nirvacana.com/thoughts/2013/07/08/becoming-a-data-sci...
Re: Developer Roadmaps
#129Earlier quoted context omitted.
Web != internet. HTTP, HTML, CSS, JavaScript, etc are web technologies. TCP/IP (among other things) are internet technologies. Web tech builds upon internet tech.
Semantics, but JavaScript itself is not a "web technology" - despite being conceived for the purpose of web scripting the original publication for version 1 even calls out that the language can be used on a variety of host environments (not limited to browsers). This can largely be seen in host environments like Node.js where it acts like any other similar language.
By that logic, CSS is not a web technology because it can also be used in GUI toolkits like GTK[1]. HTML is used in ePUB files[2], so I guess it's not a web technology either...
Would protocols that use HTTP for transport like gRPC[3] mean that HTTP is not a web technology either? I don't know what is a web technology anymore...
[1] https://developer.gnome.org/gtk3/stable/chap-css-overview.ht...
Re: Developer Roadmaps
#130Earlier quoted context omitted.
What exactly qualifies as a web technology? Isn't anything on an IP address a web technology?
Web != internet. HTTP, HTML, CSS, JavaScript, etc are web technologies. TCP/IP (among other things) are internet technologies. Web tech builds upon internet tech.
Yeah, in my OP I was meaning the WWW specifically, so the things developed for use with the WWW (HTML, CSS, HTTP, etc.) Networking (TCP/IP, UDP, etc.) are not WWW specific.
Now having said that, sure I've seen some defence projects that make use of HTTP or have internal "web"sites for managing interfaces. It's even a trend for embedded hardware to have web management interfaces (your internet router/modem is a great example).
But when I say "web", of course I was really meaning user-facing/world facing websites. That seems to be the implication behind "front end developer". Not "I make front ends for building automation systems" but "I make front ends for websites hosted on the WWW". Requires a slightly different set of knowledge imo. One is tailored for looks and UX, the other is a trade-off between minimalism, efficiency, and usability (if only this was applied more to the major sites you see on the WWW now!).