Boxxed

But you can distribute e.g. a zip file with both the run time and data in it, can't you? How is that any different from how any other game is distributed?

Why don't you want to distribute the love runtime + .love file to your users?

It is always striking to me how many of my coworkers truly do not care about solving a problem or getting things done. If they aren't exploring some new database, language, tool, or whatever then they just lose interest and try to force one of those things into the codebase.

Oddly enough, I feel like I have some friends that are the same way in their hobbies. It's crazy to me how they'll buy a new board game for $80 and play it once, maybe twice and never look at it every again.

This constant novelty-chasing is probably what both groups are really after.

I'm not sure I can make the mental leap that CEOs are making decisions based on what's best for their landlords.

Your experience matches mine exactly. Onnx seems to be relatively unknown for some reason. I feel like I'm on crazy pills -- how is everyone else delivering ML models? Are they really shipping multi GB pytorch environments? Are they using some sort of rube-goldberg machine to run things off a janky jupyter notebook?

Looks pretty cool! What happens if a program attempts a use-after-free? If this is "memory safe" (aside from leaks) then I think it sits in a pretty interesting space!

> This is an extremely cool project, but after browsing the source code a bit, it looks like it's badly in need of modernization.

Just wait until I tell you about the code in your OS, your car, and your phone...

My state requires about a half dozen vaccines (polio, HepB, MMR, ...) to attend any public school from K to college. For some reason there's some sort of collective amnesia about this and people are acting like this is the first time there's been a vaccine requirement.

Cool! Looks pretty lightweight. Skimming the code, I see some uses of strtok that look unsafe...I think a URL consisting of entirely `?` will crash.

Yep:

  Server listening at http://0.0.0.0:5000
  Parse error: HPE_INVALID_URL Unexpected start char in url
  free(): double free detected in tcache 2
  [1]    70550 IOT instruction (core dumped)  

(Opened an issue on github)

I would not recommend Dask. We use it just for simple job scheduling (that is, none of its fancy data structures) and run into issues just getting the work done efficiently. This issue, for instance, keeps the cluster from actually being utilized fully: https://github.com/dask/distributed/issues/4501. I feel like I'm on crazy pills, because it seems pretty serious yet it's gotten no attention.

Because the proportions change. OP used exadollars in his/her example to show that giving money equally to everyone evens things out.

I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents:

> I do solemnly swear that never again will my CPU have to compile ruby from source.

...yeah, why was that even happening? Why not distribute pre-built artifacts? I feel like the whole docker ecosystem only exists because people forgot how to distribute software and/or python/ruby and friends make deployment so hard.

Exactly the same as a non-YC company

I'm not entirely sure what you're saying, but it's a little bit odd to me that a non-religious person would necessarily have an irrational fear of anything you mentioned. Where, in your world view, is there room for someone who can think critically and make rational decisions? Why must all of these totally reasonable things that make up our world be feared?

Apple/Google and friends have just as much power. Seeing where people are shopping is the same thing -- I bet they had evidence of the decline of malls before anyone else, for instance.

I think we all appreciate the links but unless I'm missing something, no, it doesn't help -- what's the plan to make money? That blog post doesn't mention anything along those lines at all.

Just want to pile-on to the other replies and say yes, absolutely. When you need them as glue they're a great option with basically no alternatives -- also means your lambda functions will be just a handful of lines of code, and then you can get on with your life.

> Hackers and programmers tend to try and read the law like computer code to be "hacked" and exploited based on the letter of the law.

Speak for yourself. There are plenty of us that understand you can't take the human element out of this.

Except the same-damn-product ads also come up for things that make very little sense for re-purchase: artwork, DVDs, books, and so on.

I love it...I think that's got to be peak vaporware

This is a pretty maddening bug that I ran into: https://github.com/godotengine/godot/issues/30215

To summarize, you basically can't use the built-in viewport scaling at all because it breaks mouse input.

Not to pile-on, but I've used envkey in the past and would definitely recommend it to anyone: https://www.envkey.com/

The readme has a link to the blog post describing MIR -- it's a great read and is probably where you actually want to go:

https://developers.redhat.com/blog/2020/01/20/mir-a-lightwei...

I still hate how I'll buy something that is clearly an expensive one time purchase from amazon (such as a lawnmower or an audio receiver) and the best its dumb algorithm can come up with is, "Hey, wanna buy another lawnmower?"

I completely agree. I really like this article, which I felt like I could have written:

https://www.benkuhn.net/hard/

But how do I implement backpressure in zeromq? I've used it in production and it was great when it worked, but it was scary because its queue of messages could get arbitrarily large. I think I even saw an OoM when a service went down and something just queued indefinitely.

Edit: just checked the FAQ and apparently it will now block or drop messages. I sort of wish it would explicitly error instead of block, so as not to require the caller to queue in a thread or something.

Whatever happened to psyco? I remember it pretty much just working without any hassle and actually providing a noticeable speedup. All the mindshare is now on PyPy -- it's received enormous amounts of engineering and still seems very rough around the edges.

There are a lot of gotchas with the new GC that make me nervous about this release:

> As far as we know, ARC works with the complete standard library except for the current implementation of async...

That's not a great endorsement...

> If your code uses cyclic data structures, or if you’re not sure if your code produces cycles, you need to use --gc:orc and not --gc:arc.

Seems like this is a big onus to put on the user -- it's tough to prove a negative like this.

This is not "opposition", this is hate.

Without the behavioral data you'll just plain miss out on correlations that simply can't be described by product metadata alone. Is this a big deal? It seems like that would be one of the big advantages of collaborative filtering. I guess that advantage is probably larger on sites with a huge product variety (e.g. Amazon) which aren't really your audience.