smashedtoatoms

6 ms·

31.
by smashedtoatoms 7y ago
"We need something to remind us that we should be civil and grateful for FOSS contributions." You mean like having the legitimate risk that maintainers will take their ball and go home when people are cruel and others stand around
32.
by smashedtoatoms 7y ago
Not to mention provisioned lambdas if you're on AWS.
33.
by smashedtoatoms 7y ago
Word
34.
by smashedtoatoms 7y ago
Do you actually listen to one unique album on repeat all day every day? You ever have a month where you listen to one record, or one record's worth of tracks every day? Now you pay $10... Or play it on random to have background noise
35.
by smashedtoatoms 7y ago
I generally prefer static types. Elixir is the exception. Immutable variables and structs, coupled with OTP, make it arguably as safe for me as Typescript (whose types can lie if you get unexpected data from an api that doesn't match y
36.
by smashedtoatoms 7y ago
Same. Wsl is great. Running ides in wsl even works great, but with vscode, I don’t even do that much anymore. It’s like being on Linux for dev, but having Windows for power management, high dpi settings, drivers, etc. It’s working great, ha
37.
by smashedtoatoms 7y ago
Maybe because some mega corp will figure out how to offer it as a service, and they'll get nothing for it. I support them defending themselves with a way to maybe make money on it. If they can't eat, they can't update the c
38.
by smashedtoatoms 8y ago
I have no idea how people convince themselves to contribute to open source and/or participate regularly in online discourse. It’s basically working really hard for the easiest-to-offend and least-likely-to-appreciate-anything-you-do pe
39.
by smashedtoatoms 8y ago
Yea, this project is mostly batch processing of things, so cold starts don’t matter. There is one api endpoint that we left in go for quick responses. I thought about doing a C# to js transpile, but have not had time to look into it. That b
40.
by smashedtoatoms 8y ago
The domain experts all write C#, and I don’t have strong language preferences, so it’s easier for me to switch to C# than it is for them to switch to Go. There isn’t a real technology reason, it’s just team ergonomics.
41.
by smashedtoatoms 8y ago
1st million calls on lambda are free... then ~$1.80/million calls/month after that. No ops once you deploy... like none. Dotnet runs on it fine after being written on a Mac, with code completion and linq hints etc. No visual stud
42.
by smashedtoatoms 8y ago
I’m in the process of porting a bunch of go code to dotnet core 2.1 on AWS lambda. I’m on a Mac using vscode. I never installed mono, just the dotnet sdk. Honestly, I’ve been amazed at how good the tools have been. For cli and serverless de
43.
by smashedtoatoms 9y ago
That’s fair. Api Gateway is definitely the lock-in as well.
44.
by smashedtoatoms 9y ago
You’re spot on. It’s really not good for any scenario where an occasional random long response time is a deal breaker. It gets particularly crappy when you have lambdas dependent on other lambdas. That being said, if an occasional long requ
45.
by smashedtoatoms 9y ago
Sure, but why would you do that? If you’re running Django, set up your ec2 instance, and run Django. If you’re running lambda, don’t spin up an entire framework in it to run for individual requests. That basically defeats the purpose. You’