Consumers and shareholders like cell phones because they're shiny.
668 karma · joined February 23, 2017
https://davidcako.com
Consumers and shareholders like cell phones because they're shiny.
Javascript is "libraries" the language, for better or worse. You're comparing a language which is the de-facto language of front-end design and increasingly popular on the back-end to UI toolkits that have been around forever and still have virtually no mindshare by comparison.
HTML and javascript are the time and energy wise choice for any sort of front end design. It's just that we have shit like electron that is beyond suboptimal at tackling the issue of "native" applications (although I'd argue still a sensible choice!). Ideally we have something like react-native for the desktop, or built in html/js runtimes with platform specific bindings.
When the iPX first launched the narrative was "holy shit this phone is flying off the shelves", since then OLED stock has been falling (really good time to buy tbh), apple cuts back production, and the narrative has gone sour.
What gives?
remember, DRY. just add another npm dependency.
On a serious note, I love how in Go you can actually build a web app using the standard library. Am I wrong in thinking this should be a priority for scripting languages? I feel like adding this sort of bloat to the standard library immensely reduces the actual real world bloat, and unifies developers around particular design patterns instead of playing a game of "which library is best library?".
And I don't mean in an opinionated ASP.NET sort of way either (although to me that would still be better than the general attitude in the python/js world). Just simple tools that do things people actually want to do. Imagine if Flask and Requests were built in to python, for instance.
You don't have to teach new hires what dialect of agile model view RESTFUL event lifecycle bullshit your company speaks. In the Go model, external libraries (Gorilla, for instance) tend to be conveniences, not entire paradigms.
It's not for me, personally.
And yes, because the scariest aspect of password managers is the fact that you have basically shifted the responsibility of "I use the same password everywhere" to a different party.
Meaning you have consulted a sea of research that has compared the risk posed by password managers to keeping a mental catalogue of long, not-random-but-pretty-good character strings, using 2fa, and exercising proper security habits?
I don't think you could ever come to an objective conclusion, since the 99%-user doesn't have a near-autistic obsession with security like most of us.
For me the answer is no. I would rather have fewer technically less secure passwords than have technically more secure passwords that all live in one place. My passwords live "nowhere". There is no database breach, or peek over the shoulder that could ever compromise my entire wellbeing.
I also use 2fa wherever possible.
I use abbreviations of several different long sentences with random characters added in random positions.
To me this is far more secure than trusting a single authoritative source with 10 different random character strings that I have no real ownership of, and can all easily be stolen (or lost) at once.
I will never trust my passwords all being in one place other than my brain.
I've heard good things about Bluemix.
I don't know. I suspect being half-pregnant is a far bigger issue than the technical debt of dynamic typing, whether it stems from being slower to implement new features, spending time choosing the "correct" tech stacks, or spending more time/money hiring qualified engineers.
There's something to be said for the fact that many of the most successful startups in the world are saturated partly or fully with Python and PHP: getting features and new hires off the ground in as little time and money possible is worth its weight in gold.
I've always been very much of the opinion that the smartest way to go is making good use of FFI where it counts, and doing everything else in whatever gets code out the door most effectively. This TypeScript/Hack/MonkeyType trend just seems like a very welcome extension of that.
If it wasn't in fact enabled, it's still dumb, but to me a misstep in respecting the user and not a complete breach of trust.
Nothing about Windows RT was done in a way that indicated that they were serious about pushing it. How could you possibly sell people on a version of Windows that does virtually nothing that people would want to buy Windows instead of Android or iOS for?
I don't know if I can handle this one getting worse.
The docs are decent, but not great, and the lack of stackoverflow answers hurts.
On the contrary, I booted the exact same machine into internet recovery (which gave me the Mavericks-era Disk Utility.app) and it literally had a huge warning that the fusion drive was partitioned incorrectly, and a repair button.
Why remove important features that still (have to) exist in the underlying utility? Like this is literally an operating system designed to run on only a handful of hardware, which is why people like it.
Depression and ADHD are both related to dopamine and norepinephrine dysfunction, but depression has a strong element of serotonin dysfunction as well.
One of the defining characteristics of hyperactive individuals is their addiction to stimulation (work, learning, leisure), which to me seems like it's fed by negative reinforcement. Removal of these things sends them into a depressive state because there simply isn't anything keeping them excited (and perhaps distracted from neuroticism).
It seems like depression is kind of the contrapositive. There is the same element of dopamine dysfunction, spawning disinterest and hopelessness, but they lack the positive reinforcement of anything to pull them out of. I think this is where the sprinkling of serotonin dysfunction into the pie comes in. There's a very low level of security or confidence in any sort of endeavor.