However once you start getting into very heavily used production services, choosing a different platform becomes increasingly difficult.
482 karma · joined December 25, 2016
However once you start getting into very heavily used production services, choosing a different platform becomes increasingly difficult.
> What about good code that ships? Best of both worlds.
Right, but what is good code?
The author of this page claims that code out of the "Algebra-Driven Design" paradigm is good code. But where's the proof?
It's not enough to pull out the math textbook and give us fancy words like monoids, lattices, whatever (this is coming from someone who loved algebra classes far more than analysis classes in my math degree).
I'd really like to see real world code that uses this. And by real world code, I mean code that isn't some contrived example, code that actually runs somewhere, and provides real-world value, e.g, a semi-popular website, e.g HN, Lobsters, Reddit, or something that runs on a robot, or something. I don't know. The common theme of all of these Haskell/Idris/SomeOtherMathyLanguage posts is that almost none of them bring any real world software to the table, that has been tried and tested by the real world, e.g, consumers, customers, whatever, except for a perhaps GHC, a handful of well maintained Haskell libraries, the Idris compilers, that Haskell spam filter at Facebook.
We keep saying that functional programming is much better than any other paradigm. But the share of functional programming languages is tiny in comparison with the imperative/OO family languages, and there's a reason for that. Most functional languages are hard to use, have very little library support, and functional abstractions don't _really_ matter in the long run when it comes to bugs. Sure, C/C++/Java code is never bug free, but it's not tremendously difficult to write real-world applications using these languages, simply because of how well their memory models/object models/features map to the way most programmers think.
I just find it absurd that on these functional programming posts, everyone just keeps saying that the only good code is functional code. It's simply not the case.
I much prefer the Python 3+ approach of type annotations in source code.
I can't imagine having to look at a separate file just to figure out what the type of something is. You may say "tooling will fix this" but it's just far less overhead for everyone at the end of the day to just make annotations in source.
My more existential question is, is there really an advantage to doing static type checking in Ruby?
When I was doing Ruby, the way you can change objects on the fly, add methods on the fly, the vast amounts of metaprogramming, are types at "compile" (I know, not really) time really the same as types at runtime?
Like, it might be nice to get some autocomplete, but AFAIK tools already do that (RubyMine, others).
Honestly, do we really need to consider TikTok's rebuttals about them basically being spyware? Sure, they spy for the CCP, but Facebook spies for the highest bidder. Not sure what's worse at this point to be honest.
And I'm not leaving Facebook, Google, Instagram, or these other services out of this either. You can tout "AI" and "Machine Learning" all you want, "We want to give you the best content", etc., it's all BS. Stop it.
Unfortunately, they won't stop it, because most folks simply _do_ _not_ _care_ about TikTok being spyware, including _most_ if not _all_ the people that I know (and yes, including developers, scientists, semi-high-ranking government employees, etc.)
They're significantly easier on the eyes and they're a joy to use. I don't particularly care about color. One thing I'm wondering though, is what are the technical challenges behind building such a display?
Ideally, I'd like to be able to use an Android device that renders onto e-ink. I don't particularly care for watching videos and such - most of my time on my phone is spent sending and reading IM's (Signal, text, e-mail) rather than viewing media, so lower refresh rates is not something I really care about.
Where are the shortcomings causing e-ink displays to have very low refresh rate? Does it have to do with modern rendering technology being so well optimized for color displays that they simply are not performant for e-ink?
I feel like static typing would get in the way there, making code more verbose and more difficult to prototype while running possibly thousands of backtests (e.g, to tune hyperparameters of your model) but if that your preference, by all means, Rust should be usable for that.
Given that most FANGers are obsessed with cash, I'm pretty sure they'd say "yes" to risking their career for some sweet BTC.
I think, in the case of etcd, it would have been better for the k8s folks to fork the project and add whichever features they felt were needed to be able to use it for k8s. Instead, it seems like they swarmed the original project and added a ton of features that made it a behemoth of complexity rather than the simple tool it once was.
As if there is only one "tech Twitter" that you can concisely summarize in a "TLDR".
For another, why would I care what users on Twitter say? Is there some proven law that sentiment of Twitter users (mostly bots? I don't know) is now the sentiment of the masses?
I'm not denying that there are many students that are angered by Harvard not agreeing to lower tuition costs for online learning, but what does "Tech Twitter" have anything to do with that?
Has any one of these prospective Harvard students written something expressing their disdain at Harvard and the extremely overpriced American higher education industry?
"Twitter is where all the action happens in the tech industry".
Absolutely not. It's where a lot of people mumble garbage about random things. Are there some people on Twitter who don't do this? Of course. However, the large majority of Twitter is a cesspool and it should not be taken as a first-tier source of information.
There's just so much wrong with this post.
Emoji's everywhere, before practically every sentence and in every section. Tip to the writer - if you want to be taken seriously, do as serious journalists do, and let your prose convey the emotions you want them to convey to the reader. Emojis simply have no place in any journalism of any kind, unless you're a "Twitter power user" I guess.
Travelling around Europe, I think these were my biggest pet peeve, as an otherwise incredible and quaint city (such as Porto or Malaga) ends up being tainted with the disgusting smell of diesel fumes.
Petroleum only would be a huge improvement. Of course, electric only would even be better.
Did some HTTP call the initialization code make end up raising an exception on some unexpected status code and end up crashing the entire application?
I don't understand why this kind of control flow is acceptable. Is it documented at least? And if it is documented, how come we can't fork this SDK (seems to be on GitHub, seems fork-eable) and remove this "feature"?
On Apple though, your app might be taken down fast if you end up doing that. Doesn't mean you won't fool a few suckers though.
I have no use for social networks of any kind, but I guess if you want a non-cancerous Twitter, this looks like one.
What kind of projects are a best fit for Rust, for those who are experienced with it? Any recommendations for projects to make Rust stick?
Thanks!
It's a total joke that an app would crash on startup because of this idiocy.
Antirez, on the other hand, has had a large part in the continued development of Redis since it's inception, so like, 11 years or so (2009).
AFAIK, apart from UI improvements over the years, Git has _largely_ been the same since inception, in that you can watch a video as far back as e.g https://youtu.be/4XpnKHJAok8 and not much has really changed since those days (by the time Linus gave that prez, Junio already started running the project).
E.g, websites, video games, etc.
He was the heart and soul of the project.
It also makes me think, what would Linux be when Linus decides to step away? I kind of don't want to think about it.
Thank you to Antirez for all your hard work on Redis.