byroot

19 ms·

181.
by byroot 3y ago
> Please listen to the GitHub engineers I regularly talk with engineers that worked on that project at GitHub, some are now my coworkers. I know more about this effort than what was said publicly. > Rails 3 was found to be five times
182.
by byroot 3y ago
Sure, but the person I responded to was suggesting that Rails was deliberately holding onto memory to re-use it. That's absolutely not something Rails does, but it is something that some managed languages and some (most?) allocators do
183.
by byroot 3y ago
> had a choice to say jump to Java or a JVM-based language and scrap Ruby altogether As someone who joined Shopify 10 years ago, my perception is that it wasn't an option. At the time competition was fierce and the priority was to g
184.
by byroot 3y ago
> Is TruffleRuby compitable with Rails? Rails proper, yes. Small rails app are generally drop-in compatible, but sizeable applications are likely to run in a few compatibility issues as most gems aren't tested against TruffleRuby. &
185.
by byroot 3y ago
> Rails was initially too slow for GitHub, so they forked it, didn't use "Rails" for a while That's a weird way of framing it. They stuck with a fork of Rails 2.3 for a long time because the upgrade was deemed too cos
186.
by byroot 3y ago
Disclaimer: I'm a member of the Ruby & Rails infrastructure team at Shopify and Ruby committer. > Shopify isn’t hiring people to contribute to MySQL or Redis internals You are not wrong, but the main reason is that contrary to R
187.
by byroot 3y ago
This person is incorrect, but even if they were correct, that wouldn't be a framework thing. Memory management is handled by the language.
188.
by byroot 3y ago
> Ruby processes don't return the memory to the system That is not correct. Ruby do unmap pages when it has too many free pages, and it obviously call `free` on memory it allocated once it doesn't use it. What happens sometime
189.
by byroot 3y ago
Shopify bigger repos are deployed pretty much every 30 minutes. As you point out most JITs struggle in these conditions. But YJIT warms up extremely fast, and is able to provide real world speedup to these services almost immediately.
190.
by byroot 3y ago
If you properly scope to the Computer & Electronics category to avoid matching "Django Unchained" the graph is quite different: https://trends.google.com/trends/explore?cat=5&date=all&q=%2...
191.
by byroot 3y ago
Yeah, you can use it to implement a simple (but not necessarily very performant) LRU: https://github.com/SamSaffron/lru_redux/blob/037ee594aded597...
192.
by byroot 3y ago
The incident was recorded though: https://status.slack.com/2023-08-17 I suspect they didn't consider that it impacted their SLO because it wasn't impacting 100% of their customers. That's the problem of statu
193.
by byroot 3y ago
No, but for that use case you have EVAL which execute an arbitrary lua script on the server. https://redis.io/commands/eval/
194.
by byroot 3y ago
Not the person you are asking but, 16 times seem like a lot, however it's going to heavily depends on how good the VM or JIT is at inlining. Because `Array.forEach` is one method call for each iteration, when `for loops` stay on the sa
195.
by byroot 3y ago
For people who don't read French, yes on paper there is no legal obligation to have any kind of ID on you. However, police forces are allowed to ask anyone their identity without any reason, and if they can't justify of their iden
196.
by byroot 3y ago
Les Soulèvements de la Terre: https://fr.wikipedia.org/wiki/Les_Soul%C3%A8vements_de_la_Te...
197.
by byroot 3y ago
Maybe I'm being too optimistic on the majority of them not approving such a law, but in many countries, notably Germany, I think that wouldn't fly, but I may be wrong. As usual these laws start by being applicable to only terroris
198.
by byroot 3y ago
No it doesn't. EU is a large union of 27 countries. France is having a big authoritarian turn that started after the 2015 terror attacks, and it accelerated under Macron. That law would certainly not pass in the majority of EU countrie
199.
by byroot 3y ago
> over emphasizes the cost of platform transition while downplaying the operating burden of not modernizing. Given that I work on the Ruby Infrastructure team at Shopify, I think I have a well informed view on both the cost of transition
200.
by byroot 3y ago
> Isn't "it's comparatively slow" what people usually mean with "doesn't scale"? If that's the case, then they are misguided. > You can scale anything with enough hardware No, some architectures
201.
by byroot 3y ago
> Disclaimer : my career has mainly been on compiler/runtime and other infrastructure related stuff, so not much of a business logic/web dev kind of guy. That probably explain your surprise. This question comes up extremely oft
202.
by byroot 3y ago
Not really. Even if it was somehow funded, the original author may still want to stop maintaining it and hand it over to someone else. So it's an entirely different issue.
203.
by byroot 3y ago
It depends from conference to conference, but generally speaking "keynote" means: - The very first or very last talk of the day. - A larger time slot, looking at the Rustconf 2022 schedule, keynotes are 45 minutes long, regu
204.
by byroot 3y ago
But you can emit as many 103 as you want. So you can start by sending the statically known assets, and then emit an extra 103 each time you are at the stage where the other assets are known.
205.
by byroot 3y ago
> Early hints solves a different problem I think it saves the same main problem which is to trigger assets download early. However you are right streaming the response has a few extra advantages. I still think getting most of the results
206.
by byroot 3y ago
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103 As they mention in the article, the main goal of streaming your response is to deliver the <head> tag to the browser sooner, so
207.
by byroot 3y ago
I wonder why they didn't consider 103 Early Hints instead, as it solves the same problem in a much more elegant way, and doesn't require to re-architecture your application.
208.
by byroot 3y ago
All I’m saying is that autoloading isn’t the reason.
209.
by byroot 3y ago
Your code is supposed to be loadable in any order. If not, you are doing something wrong and you could experience just the same issues without it. But if you don't like autoloading, you can turn it off with just `config.eager_load = tr
210.
by byroot 3y ago
> Require branches to be up to date before merging Because this really doesn't scale well with the number of developers. For larger teams the solution is to use a merge queue, e.g. https://shopify.engineering/success

More ›