groestl

33 ms·

211.
by groestl 3y ago
> Is there a term for this where outputs are eventually fed back into training, at a ever increasing rate? Consciousness
212.
by groestl 3y ago
"Es war sehr schön, es hat mich sehr gefreut."
213.
by groestl 3y ago
"It takes an admin to take down a server, it takes a configuration management system to take down a site".
214.
by groestl 3y ago
There's opportunity cost, that's true, and I'm sure one can show that the most optimal situation in this case would be everyone on the world using the same office suite (i.e. free trade is optimal), _provided_ non-US countrie
215.
by groestl 3y ago
Yepp. The only money that might "cost" something, to a nation state, is money that leaves it.
216.
by groestl 3y ago
I check those, and I don't consider myself special at all. There must be half a million technical people out there checking those boxes.
217.
by groestl 3y ago
> like how one of our skin cells don't understand how the body works And how surprising would it be if, in one of our skin cells, there would be a life form that, through their scientific advancements, actually understands how the b
218.
by groestl 3y ago
And before crawling into it.
219.
by groestl 3y ago
I do that with my kid. For funsies. Also high in the list: snake bites foot (to put on his tights).
220.
by groestl 3y ago
> can be likely handled by a single well configured server. A single core, actually, after JVM JIT kicked in.
221.
by groestl 3y ago
Agreed, this is true, for anything needs to independent from calenders. You find those problems typically on lower levels, in systems engineering (and I'm not surprised you mention microcontrollers, I know many of those from there as w
222.
by groestl 3y ago
> "$DATE" was meant to imply "$DAY $TIME $ZONE." I'm curious, what does the "number of milliseconds since" do, then? If it's about intervals, and it has some human connection, you're still in
223.
by groestl 3y ago
> Store everything as "number of (seconds|milliseconds|whatever) since $DATE" This itself is a falsehood, at least as such a strong statement. You'll avoid some of the falsehoods in the text, but as long as humans and poli
224.
by groestl 3y ago
[typically found in the terms of service] [Let's break it down for clarity] [This type of clause is common in the terms of service for online platforms] [It’s important for users] This comment reeks like ChatGPT generated content, tbh.
225.
by groestl 3y ago
Not legally.
226.
by groestl 3y ago
"commercialize the User Content in any way that Vultr deems appropriate" is not at all related to CYA wrt crawlers.
227.
by groestl 3y ago
Have all my stuff there (bare metal), can recommend.
228.
by groestl 3y ago
"an adversarial position" is the only position you should assume when interpreting legal texts. After all, if push comes to shove, your the actual adversary. And in any other case the legal text is not needed.
229.
by groestl 3y ago
Or they used AI to generate their new TOS and didn't proofread...
230.
by groestl 3y ago
That's the basis for any business model where you are the product.
231.
by groestl 3y ago
> I've occasionally edited them by hand. Yeah, usually when the quoting was f'up.
232.
by groestl 3y ago
That's eerily similar to what (green) threads are.
233.
by groestl 3y ago
> It just doesn't seem to have caught on as the standard exception handling idiom. Not only that, but there is heaps of code which is correct in the presence of errors (after all, Go developers tend to obsess a lot about them), but
234.
by groestl 3y ago
> you'll postpone handling it as much as you can. Which is exactly what you should do if you are in the game to build reliable complex systems. See my lengthy post here https://news.ycombinator.com/item?id=39808367
235.
by groestl 3y ago
> Bubbling up errors is not handing them. And yet, this is exactly how you learn to design dependable systems. You try to stay in fail early territory as long as possible (bubbling up errors, failing every system level on the way), until
236.
by groestl 3y ago
> In principle, exceptions are a streamlined version of tossing err up the stack without any embellishment. This is exactly what I meant. It's "handling", when viewing the consuming function as failing system. It's no
237.
by groestl 3y ago
> - Use errcheck and friends to ensure errors are not ignored. - Never dereference the left hand return value if the right hand is an error. This itself is a very concise argument for exceptions. Automatically checks errors are not ignor
238.
by groestl 3y ago
In Austria, we just don't have tuition fees, which also avoids these types of shenanigans :)
239.
by groestl 3y ago
Classic tragedy of the commons.
240.
by groestl 3y ago
"0 mention of Bitcoin" might have sparked a discussion, but: as a Millenial I feel your mention of "Boomer" is unwarranted, and as a dev in fintech I very much understand blockchain tech, but "the future of the mone

More ›