125 karma · joined June 26, 2015
Try taking a close look at how the US budget actually breaks down. It's quite a task since it's an enormous budget. But, if you boil it down to a pie chart, you'll find that we spend an absurd amount on "defense", most of which is wasted. You'll also find that Congress will routinely spend enormous sums of money - in the trillions - on things that aren't health care (e.g. wars & combat, economic bailouts, etc.), without ever asking how it can be afforded, and it doesn't cause the whole system to come crashing down.
It's about priorities, and finding legislators to elect who share the correct ones. I believe that we'll get there, slowly, one funeral at a time.
Sounds like a nice little side project.
At that point, you rely on the body content to tell you what the service correctly determined for you. A result that the user doesn't like is way different than a result that comes about because something was done wrong at the client side (4xx) or a failure on the server side (5xx).
Things I do that are only possible in Android: 1) I script some behaviors using Tasker. One example is that I have a script that takes it out of vibrate mode and turns on the ringer if I'm home (GPS), the phone is plugged in, and it's between the hours of 9am and midnight. 2) This requires root, so it might not be worth the trouble for you, and it's not available on every phone. But, I've managed to make my default home screen completely blank. My primary "launcher" is an app called "Pie Control", which doesn't appear unless you touch an area of the screen, which you can set. I can also swipe up to get a screen with all of my apps - The default behavior of Nova Launcher.
It's not just customization. Really, the sky is the limit when it comes to what you want the phone to do. With an iphone, the limit is the constraints of Apple's design.
I might think differently if confronted with a huge API surface area to build off the bat, but I haven't run into that yet.
Maybe try getting started on both, and see which one is easier or more comfortable?
It's very possible for VSC to improve in these areas. In fact, I'd love to see an "Atom mode" that changes the UI/UX to more closely resemble Atom (and, somewhat by extension, Sublime). You laugh, but there's a reason that every editor takes a swing at a "vim mode". People get comfortable with the aesthetics of their tools.
Yeah, there was a sort of "golden age" of innovation where we went from jQuery -> Angular 1 -> React, with Elm, Ember, and Angular 2+ as sidecars. And, the common libraries and tools have also slowed down in the same way.
We've finally solved a lot of the big problems, I think. Advancement will never end, but I think we'll be able to keep up with it from here on out.
Yes, you can use the native API for some of what jQuery does. but, don't let anyone here fool you - the full API of jQuery has not been completely replaced by the "vanilla" API. And, jQuery's API is still much better designed.
Now, if you're building something Very Large, you don't want to lean on jQuery alone. If you're using a framework whose footprint includes what jQuery does (anything with a virtual DOM and automatic updates, for example), then there's no point in also using jQuery.
There's room for all of the tools. Use the right one for the right job. Do enough front end development, and you'll know which one to pull out when you need it.
What's more, all the things that obviously would make money are probably already saturated by something that Amazon does.
It's a real shame.
I'd ask an opposite sort of question: How many 30yo+ senior developers does your company employ? If none, then why not?
Wisdom is in ever shorter supply in technology. Frankly, having people with deep experience on hand is a source of competitive advantage.
With all that in mind, I think that we shouldn't blame "insanity" on the very tools that have been employed to control insanity. If anything, such a viewpoint tells us that maybe the attempts of today aren't the full answer, so there will be more tries tomorrow.
I'll leave you with these things: 1) If the only thing you're doing is creating a web page that serves as a thin visual layer over REST- or CRUD-based services, consider going back two generations to Backbone. Seriously. It does a few simple things for you, and lets you handle the rest in any way that you see fit. Those simple things may be the only thing that your app does. I suspect that this would be true for half of Silicon Valley. But, it goes against the constant pursuit of the new and shiny.
2) If your browser does more than just send a few CRUD commands from the user to a server, then maybe it's time to look into what's good about these frameworks, instead of just considering them "insane". Everyone has their own good parts and pain points to be addressed, and all these tools were built with the best of intentions, to solve specific classes of tough problems, which may happen to be yours. Look at the success and failure stories, and see who's happy with their decisions about their tools, and which problems were solved with what framework.
3) For those people telling you "just use vanilla JS", I'll leave you this: Any sufficiently complicated vanilla JS program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Angular or React.
I really hope I'm wrong.
So, yeah. People hated using it for email. More than once, I built a better email client for it, and people were suddenly a lot happier with it. There wasn't as much that I could do for the calendar app, which had serious core deficiencies.
To be honest, I never understood all the hate, though. Don't get me wrong - no one knew where it was lacking better than I. And, it's been a "dead" product for many years; it would be silly to ever recommend it now. But, executives who never had to even touch the thing would enter a company, and declare that, "We MUST move from this to Microsoft products!" And, the alternatives would always be far worse. (Think Sharepoint, for example.) I'm not even sure that google's productivity products are that big of a step better.
Notes solved a lot of hard problems for large organizations, all at once. It wasn't pretty, not was it ever really that fast. But, it enabled business - particularly non-tech business - the ability to automate things in the blink of an eye, for instant improvement.
I think that we could all learn a thing or two from looking at why it was so popular in its day, and maybe keep just the good parts in what we do.
I happen to like Semantic UI a lot, but you can also consider something smaller and less proscriptive than Bootstrap, like Skeleton or UIkit.
Yes, "you might not need jQuery". But, the first time you have to log real hours fixing a cross-browser bug that the jQuery team already took care of, I'm fucking firing you. Choose wisely.