spion

7 ms·

31.
by spion 2y ago
That promise doesn't really make sense to me - although partial compilation will likely ameliorate most migraiton pain for library dependencies if they come pre-compiled with the compiler. Code written with the react compiler in mind w
32.
by spion 2y ago
If you have a very large project which uses MobX, I don't think the amount of warning matters. You'll most likely have to (eventually) completely rewrite large amount of code, to the point where it might be easier to migrate to So
33.
by spion 2y ago
Also, because next broke emotion, toolkits such as Mantine broke backward compatibility in order to move off of emotion, so second order instability effects still affect SPAs
34.
by spion 2y ago
Important or not, libraries you depend on may jump on it and abandon backward compatibility
35.
by spion 2y ago
react compiler breaking mobx is purely spa; progressively stricter rules of hooks too. Its bad.
36.
by spion 2y ago
> My react code now doesn't look very different to my react code in 2019 Server components, Next application directory breaking emotion for styling, stricter rules for hooks, the compiler breaking change tracking libraries such as M
37.
by spion 2y ago
> Implementing a basic "useState" and "runFunctionComponent" is easier than most third-semester CS assignments. I'm not sure it is. There is a global dispatcher that finds the right component state to use and inc
38.
by spion 2y ago
IIRC reading the React source code became quite a feat around the time fibers were introduced.
39.
by spion 2y ago
You can use a language / compiler / static analyzer that restricts side-effects.
40.
by spion 2y ago
The setup / overhead is for the initial render, but after that I'd be surprised if O(N) defeats O(1) even with a bit of a bigger constant (given a sufficiently large N). Also, given React Fiber, I doubt that those 1000 calls will
41.
by spion 2y ago
The one place where signal based fine-grained reactivity still wins are lists. Updating the "done" state of a single todo item nested in a list of todo items still causes an entire list (of possibly hundreds of items) to re-render
42.
by spion 2y ago
Not really blaming, more like wondering how things would turn out. Probably would only delay the move to the cloud a little bit, and perhaps make AI less capable.
43.
by spion 2y ago
You're selecting for people who feel they're priviledged enough to reach out to support and ask for bill forgiveness even when they may've messed up, repeatedly. This does select for something but I'm not 100% sure &quot
44.
by spion 2y ago
Was he though? If we didn't have GPL perhaps at least our software and data would've still been on our computers instead of a privately owned cloud...
45.
by spion 2y ago
Nothing that exciting, I'm afraid.
46.
by spion 2y ago
I've never used it with a rooted device! :) I don't think there should be any significant difference in funcitonality, other than perhaps the set of directories accessible. In general, you should be able to access anything that yo
47.
by spion 2y ago
Hello, maintainer here. Happy to see this little project on the front page of HN. Unfortunately it hasn't received the appropriate attention from me lately, mainly because of the difficulties of running tests (and the android emulator)
48.
by spion 2y ago
There is honestly not much to learn, and that might be part of the appeal. At its core, JS is a relatively simple dynamic language with a clean syntax. Despite the clean syntax there are quite a few quirks in how some of the internals work
49.
by spion 2y ago
- Fewer people getting spammed - The people who receive the cold email are (increasingly) more likely to be at least somewhat interested - A human really wrote personalized emails, instead of trying to trick people into believing that
50.
by spion 2y ago
To make this less spammy, the person sending out the emails could've instead used AI to filter through a smaller set of people where their product is likely to generate very high interest, based on a prompt containing the product descr
51.
by spion 2y ago
Wayland is almost-ready. This is what I needed to do to switch (caveat: this is ubuntu 22, so I may be 2 years out of date): - Accept inability to use monitor color profiles (this is still WIP) - Accept inability to use full-screen sharing
52.
by spion 2y ago
Monads being monoids isn't very interesting in a practical sense - e.g. just because you can associatively combine steps in a program isn't very interesting. (We do it all the time when we extract a subset of instructions as a pro
53.
by spion 2y ago
They are interesting in purely functional languages like Haskell because they allow for side effects without sacficicing purity and referential transparency. Rather than allowing side effects, you describe the program as, say, specs for the
54.
by spion 2y ago
Same. Coincidentally, wayland is pretty fast.
55.
by spion 2y ago
It depends on the context. In some context, they might actually jump out. In some context, even if they don't, it might be fine, because the larger modules containing the code already have excellent tests and are solid and stable
56.
by spion 2y ago
I could make the same argument for not using DRY. The DRY-ed code is hard to change, programmers feel honour-bound to keep using it and tweaking it by adding a variety of parameters to more and more cases, and at the end becomes impossible
57.
by spion 2y ago
This really makes me think we should be focusing on cost/benefit, risk/reward, pros/cons at all times. If we have a bug in these 5 copies, will it be too hard to fix in all of them? No? What about these 10 copies? If that sou
58.
by spion 2y ago
Its not about OOP but the probability that those two functions will diverge. Linked elsewhere in the comments too, this article ( https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction ) is probably be
59.
by spion 2y ago
"this will be done tomorrow/next week/in three months" This type of answer is also possible if you can agree on the desired confidence. I've found that 95% confidence is sufficient for most cases, but that number wi
60.
by spion 2y ago
For cases where the tech stack is in some ways unfamiliar, we create research stories where the goal is to do the quickest thing possible to answer questions about the tech. This is typically timeboxed by the max time we'd be willing t

More ›