beders

27 ms·

301.
by beders 5y ago
Yup, scary beasts. If you get sucked out of the kayak, the only way to escape those is to get rid of your life vest and try to catch the outflow deep underwater. At least according to anecdotes.
302.
by beders 5y ago
It is not overhyped at all. It is misunderstood. If you pick an API stack, consider your users. If you build an API for general consumption that you want to gradually evolve and that should remain valid years from now, a RESTful API with HA
303.
by beders 5y ago
Looking forward to the next article 10 years from now. Will code written now be incomprehensible then? One thing seems clear: We won't be using webpack, react or any other current tool. I'm not sure how organization can shoulder
304.
by beders 5y ago
> As for waste, it isn't as big of a deal as you might think. If John Oliver dedicates a whole episode to that problem, it is kinda a big of a deal, isn't it? Leave it in the ground. WWS is sufficient to transform our energy sy
305.
by beders 5y ago
This is an article, not a paper.
306.
by beders 5y ago
I was willing to take the downvote hits. This narrative of "we need a baseload" or "the sun doesn't always shine" is just not countered often enough. WWS would be sufficient for the majority of countries around the
307.
by beders 5y ago
A almost 1% failure rate is not safe. Not by a long shot. Would you fly planes that had these failure rates? Also, it is the potential of catastrophic events that is the issue here. Look at the Diablo Canyon Nuclear Power Plant on the centr
308.
by beders 5y ago
That is not true. Not by a long shot. We don't need nuclear at all. https://web.stanford.edu/group/efmh/jacobson/Articles/I/Coun...
309.
by beders 5y ago
There are still radioactive boars roaming the forests of Bavaria. Just saying.
310.
by beders 5y ago
Just to keep in mind: StackOverflow deliberately removed Clojure from their surveys. People who embrace it are loving it to bits. Also Haskell and Clojure are not even in the Top 50 programming languages according to TIOBE. "Languages
311.
by beders 5y ago
From the web page: "Application developers should care about data – not SQL" That is fundamentally wrong - or at least - it is very limiting. Think very hard about adopting a framework that tries to shield you from SQL. Because at
312.
by beders 5y ago
While I like the idea of Rust, having to (re)-learn all these subtleties seems daunting (just look at the table comparing dyn vs. box vs. arc vs. references etc.) When I moved to Java 1.0, coming from C/C++, I hated the performance los
313.
by beders 6y ago
I find those discussions around how secure this app is or not is pretty funny. The answer is: It's not. Not for any kind of end device attack. You are literally typing a note into a text field provided by the OS. You are reading it in
314.
by beders 6y ago
We are currently settling for something in between: EQL (using Pathom resolvers) This gives front-end devs the flexibility of GraphQL, composability for free (EQL's DSL is just a data-structure you can manipulate easilty) and is databa
315.
by beders 6y ago
Tools have a very hard time understanding arbitrary gradle scripts. Since your config language is Turing-complete, you can easily subvert any kind of assistance from tools like Intellij IDEA. Parsing XML on the other hand and adding some se
316.
by beders 6y ago
Minimizing the impact and long term effects of this is despicable. How dare you spit on the grave of the 1368 people that died as a direct and indirect consequence? Nuclear power is expensive, unreliable and the sooner we get rid of it, the
317.
by beders 6y ago
This is so true for every bug tracking system I ever encountered in any company. We called it the P3 graveyard. And there's always that lingering feeling that there are few nuggets hidden in there that would resolve the majority of the
318.
by beders 6y ago
Yeah, never upgrade, fork and get the security updates somehow in that new fork. Not very convenient. Semver is not an excuse to break your clients. The reason given was "code size and keeping the API surface small". Both are bogu
319.
by beders 6y ago
This is great! What is not so great is that Google's closure team (not be confused with clojure) decided to remove various functions, making breaking changes - for no obvious reasons other than saving a few lines of code. Example Thing
320.
by beders 6y ago
Solar is now the cheapest form of energy. Ever. Before you try to sink billions into nuclear energy, explain why we can't do it with solar + storage alone? Just one good reason. I've yet to hear anything substantive. All I keep h
321.
by beders 6y ago
Company is dividendfinance.com Keep an eye on /r/clojure or the #remote-jobs channel at clojurians for details
322.
by beders 6y ago
We have 4 open reqs for Clojure devs. It's still an attractive platform to be honest. Our frontends and backends are Clojure/ClojureScript and we wouldn't want it any other way
323.
Show HN: Who Next? - you provide a list, we pick the order(whonext.monoid.us)
2 points by beders 6y ago|1 comments
324.
by beders 6y ago
Finally solved: Who should go next on (stand-up|reports|doing dishes)! This completely over-engineered app will delight you by generating a new sequence of names every time so you'll have an answer if someone asks "Who's next
325.
by beders 6y ago
What's the allocation pressure in comparison? Is this a time for memory optimization? i.e. am I sacrificing anything using this?
326.
by beders 6y ago
Obvious. But not what I meant. I meant that it was a conscious decision to use an object pool and re-use objects. That doesn't happen with immutable by default languages. Ergo, these particular kinds of bugs just don't happen.
327.
by beders 6y ago
object pools == mutability (why else would you keep objects around in a pool)
328.
by beders 6y ago
"While the immediate risk has been mitigated, we worked with the maintainer of Unicorn to upstream the change to make new requests allocate their own environment hashes. If Unicorn uses new hashes for each environment, it removes the p
329.
by beders 6y ago
A mutable object 'env' was shared across threads.
330.
by beders 6y ago
Another case where using immutable data by default would have prevented any shenanigans. It also shows the highly entangled relationship between state and complexity. (in this case, the env object) Immutable data forces you to design your s

More ›