adql

17 ms·

181.
by adql 3y ago
> In terms of how hard it is to get places you really want a delt-v map[2]. By that metric Venus is the closest at 640 m/s from Earth intercept to Venus intercept. Well, that's also a minimum that changes over time. It might be
182.
by adql 3y ago
It should be like that from the very beginning, any and all configuration management systems that chose YAML as base instead of DSL (even if DSL is just a subset of Python or Lua) have same problems.
183.
by adql 3y ago
The negative experience comes entirely from bugs in tools, not lack of features
184.
by adql 3y ago
> The number of requests sent exceeds the quota limit. lmfao google can't host a fucking static page
185.
by adql 3y ago
Sooo if you have root on rPi you can permanently brick it by writing invalid key to OTP ?
186.
by adql 3y ago
And other point I also seen used to lie about cloud cost is saying you save so much on engineers. ...while forgetting to have sane on-call rotation for cloud you also need at least 3 people on that rotation that are also clued in on cloud
187.
by adql 3y ago
If the end result is the same you're just wasting components that already are builtin into most microcontroller. And you'd need to remember to not use autonomous part of microcontroller (like a timer output) to implement it. Con
188.
by adql 3y ago
I prefer "One way to format everything", it just cuts so much needless whining if everyone just uses same formatter with little to no settings. ... and having curly bracers instead of the whitespace nonsense. Using invisible chara
189.
by adql 3y ago
I think that is fine if language also does directory = namespace
190.
by adql 3y ago
> and they should be upfront about that. Do you need a screenshot and red box around the text or would you believe me if I tell you it is written on their lambda pricing page near the beginning ? It's also written in docs about conf
191.
by adql 3y ago
I kinda thought about making "monolithic lambda", where there is just interface to get the request, respond to request, logging, and maybe some queue to talk with other components, for some of my personal tools. Basically cut down
192.
by adql 3y ago
That's honestly more impressive than the UDP stuff
193.
by adql 3y ago
It's ~$1.5 chip that's comparable with other ~$1.5 ARM chips (~$1 for chip, let's say $0.5 for 512kB NOR FLASH) In fact if you want more than say 250kB of RAM, currently the cheapest alternative on Mouser is ~$5 (STM32F730V8T
194.
by adql 3y ago
When that wasn't true ?
195.
by adql 3y ago
> It's not really the same spot in that your paying monthly rather than upfront. Devs tend to think about total $, the business/accountants do care about Opex vs Capex. You can buy physical servers in leasing ,turning it into o
196.
by adql 3y ago
And that you can also lease servers directly from vendors like OVH so you don't even need to bother with the "drive to datacenter and install it" part. It's more expensive but still far cheaper than cloud
197.
by adql 3y ago
That kinda begs the question "why not watchdog?". Most MCUs have one
198.
by adql 3y ago
Decision paralysis is a thing - while having digital multieffect might open you to near-unending combination of effects, exploring within limits of few single function (not neccesarily analog) pedals is less complex. Also some say some quir
199.
by adql 3y ago
Physical digital ones are a thing
200.
by adql 3y ago
I'm annoyed that they just call MOSFETs FETs. There are different types dammit!
201.
by adql 3y ago
>Like, did they even think about cost when designing this the first time? Obviously no, only after managers complained.
202.
by adql 3y ago
> This is not a discussion of monolith vs serverless. This is some terrible engineering all over that was "fixed". I feel that's like 95% of the "we migrated from X to Y and now it is better"; most of improvement
203.
by adql 3y ago
well, they have no incentive to not make you pay for CPU time on your application startup
204.
by adql 3y ago
That is probably the best use case for microservices (althought I'd just call them "services" at that part). That assuming they are big enough to warrant that in the first place. IMO if it is a dozen unrelated endpoints but
205.
by adql 3y ago
When they say k8s is "easy" they mean "for developers", not people/automation running it. Like, compared to implementing hitless rollback over bare metal services k8s way is "easy", just set some stuff in
206.
by adql 3y ago
They really don't unless you routinely put a bunch of tiny self-contained apps. The "pain" of figuring out how to deploy your "normal app" quickly amortizes over just how much easier and more reliable code is.
207.
by adql 3y ago
It's way too easy to just add a lot of friction if you go too far. I also think it would be way healthier if teams acted as "maintainers" rather than "sole developer" of a service. For example if team A wants featur
208.
by adql 3y ago
>Another pain with monoliths is that they can only be deployed if the entire monolith is passing all tests. When you cannot deploy your changes because someone else on an entirely orthogonal team broke something in the monolith which is
209.
by adql 3y ago
> Do you think the Lambda team want people to use as many of their services as possible even when it's not actually appropriate and there are better architectures and approaches available? They most definitely want to as that would
210.
by adql 3y ago
Kinda depends if you can run replication from aurora to regular database

More ›