Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mgdev
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
61.
▲
by
mgdev
2y ago
Update: they contested my chargeback. Going through round 2!
62.
▲
by
mgdev
2y ago
Unless it can die. And understand death. And adapt behavior to avoid death. Of course, that raises a whole new set of issues.
63.
▲
by
mgdev
2y ago
I was charged $5k due to a bug on Oracle's side. I initially escalated to support. Similar thing - they said there was nothing they could do, and that I needed to cut a ticket to another team... one which I couldn't contact. They
64.
▲
by
mgdev
2y ago
Over-marketed the technology, under-marketed the benefits.
65.
▲
by
mgdev
2y ago
Hear, hear!
66.
▲
by
mgdev
2y ago
I'm just now discovering Koka. I'm kinda blown away. I'm also a little sad at this defeatist attitude. What you said might be true, but those things are solvable problems. Just requires a coordinated force of will from a few
67.
▲
by
mgdev
2y ago
Consider that the type of person who can't save enough money, no matter how much they make, is probably not the kind of person who will be successful in business.
68.
▲
by
mgdev
2y ago
I'm personally a fan of FP. It offers clear benefits: simplified parallelization, improved testability, and reduced side effects. These advantages often lead to more maintainable and robust code. However, FP's benefits can be over
69.
▲
by
mgdev
2y ago
I'll add that if a lot of people actually did start using it for this purpose, they could probably just productionize the thing they actually use for this, which is essentially their own version of etcd, but with Paxos instead of Raft.
70.
▲
by
mgdev
2y ago
You must be fun at stand-ups.
71.
▲
by
mgdev
2y ago
I'll concede that "it" was ambiguous. Though if you take the most literal version of what I said, it would be they'd shut down S3, which clearly isn't true. We can continue to debate whether or not I (who worked on
72.
▲
by
mgdev
2y ago
Totally. I'm not advocating that people don't ever use it for this. I'm just saying that from a pure resource perspective, it might be one of the least resource-efficient mechanisms for doing this. As others have pointed out,
73.
▲
by
mgdev
2y ago
It's almost perfect. If it were strict C in stead of C++ I would probably be in love.
74.
▲
by
mgdev
2y ago
I never said they would kill the feature. I said they would shut down the behavior. They can do that through economic incentive. (Source: I was on the S3 team. Opinions my own, etc.)
75.
▲
by
mgdev
2y ago
I agree that the JVM is an amazing piece of technology. But the ecosystem that exists around the JVM also comes with both a bunch of awesome libraries, and a whole bunch of cruft and ceremony. If, like Clojure, you're trying to pull in
76.
▲
by
mgdev
2y ago
They introduce economic incentives. :) By way of example, a little over a decade ago a famous online streaming company used to upload all of their video masters for transcoding. This process involved a huge upload and a huge workload, follo
77.
▲
by
mgdev
2y ago
If everyone started using S3 for this purpose, they would shut it down pretty quickly. Small objects (especially small hot objects) are actually problematic in S3. They cache them in the keymap instead of retrieving from block storage. But
78.
▲
by
mgdev
2y ago
I agree! And I still love it because it's what allowed me to sneak a Lisp into not just a Java shop, but the Java shop: Oracle.
79.
▲
by
mgdev
2y ago
Will check it out!
80.
▲
by
mgdev
2y ago
I'll check it out, thanks!
81.
▲
by
mgdev
2y ago
Ahh, the siren song of Lisp I wrote Lisp (Clojure) professionally for several years. It was the most fun I ever had. My only problem was it was an ongoing battle to convince people - especially management - that I wasn't crazy. Sure, I
82.
▲
by
mgdev
2y ago
This is a very expensive way to do leader election, at least from an infrastructure perspective. This is because you're essentially pushing the problem down to S3, which does its own leader election in a way that is waaaay overbuilt fo
83.
▲
by
mgdev
2y ago
This is one of the reasons why I disagree with point three of the article. The emotion that AWS helped overcome was frustration that individual developers faced when trying to build something new. Suddenly, hardware was in their control fro
84.
▲
by
mgdev
2y ago
I disagree with point three. Engineers do make purchases based on emotions, just different ones than typical consumers. Engineers are driven by emotions like: - Desire for intellectual respect: Choosing innovative products to appear forward
85.
▲
by
mgdev
2y ago
It's cool to read this. One interesting tidbit is that during the period this author writes about, AWS had a roughly 4-day outage (impacted at least EC2, EBS, and RDS, iirc), caused by EBS, that really shook folks' confidence in A
86.
▲
by
mgdev
2y ago
I hate stuff like this. It's so incredibly brilliant that it spoils me for mainstream tech, but it's never actually "done enough" for mgmt to feel comfortable adopting it in any capacity. (See also: Unison https:/&
87.
▲
by
mgdev
2y ago
I suppose I had my order of operations turned around. Lard substitute first, war lubricant later. https://www.thedailymeal.com/1386775/crisco-facts-why-people...
88.
▲
by
mgdev
2y ago
> Haynes passes Leonardo a rusty, dented Crisco tub, which he and Price use to lubricate the pipes they work on. I can't believe someone decided, "Hey, we should take this stuff we built as a submarine lubricant, and market it
89.
▲
by
mgdev
2y ago
Welcome to the trough of disillusionment.
90.
▲
by
mgdev
2y ago
This is the cost of building a proprietary distribution network. Now they need to monetize it.
More ›