bwilliams

6 ms·

1.
by bwilliams 4mo ago
I think that's a factor for sure, but is less important (generally) as the price gap increases. The Steam Deck also has a disadvantage in that only some of your existing library will be playable on the device. There's definitely a
2.
by bwilliams 4mo ago
I love my Steam Deck aside from the quality control issues I ran into, one of which required an RMA. It's really hard to justify $1000 for it when the Switch 2 is $450 (soon $500). I do think there's a bright future for PC handhel
3.
by bwilliams 4mo ago
Same. It’s the best ebook experience I’ve had so far despite its size and I’ve tried a myriad of ereaders. The only missing feature is a backlight for reading at night.
4.
The Inverted Reactivity Model of React(chrlschn.dev)
1 points by bwilliams 9mo ago|0 comments
5.
by bwilliams 1y ago
There's definitely a number of reasons, but I vividly remember _struggling_ with Ember data at the time. The framework itself was already complicated and the data management story felt immature and rigid in addition to complex. That de
6.
by bwilliams 1y ago
> The best part about blog feeds? It's just an idea. There's no central authority. There's no platform. I think this is blessing _and_ a curse. I had an idea that I built a while back that centralizes RSS feeds so you get
7.
by bwilliams 1y ago
You can have a modular monolith with multiple entrypoints that enable autoscaling of independent "deploys".
8.
by bwilliams 2y ago
I had the same thought when reading the article too. I assumed (and hoped) it was for the sake of the article because there’s a stark difference between idiomatic code and performance focused code. Living and working in a large code base th
9.
by bwilliams 2y ago
Great article, memoization is pretty complex and full of trade-offs. We recognized a lot of these same pitfalls as we worked through making memoization a consistent and common pattern in our (very large, monolithic Rails) codebase via a `me
10.
Show HN: I built a social RSS feed aggregator (with Go, Tailwind, and Htmx)(onread.io)
3 points by bwilliams 3y ago|0 comments
11.
by bwilliams 3y ago
I’m not sure if it changed, but Crystal was limited to a single core which I imagine made it easier to choose Go over Crystal. That and I’ve found that folks often aren’t very receptive to Ruby like syntaxes initially.
12.
Multi-Page Web Apps(adactio.com)
1 points by bwilliams 3y ago|0 comments
13.
by bwilliams 3y ago
If we can’t have native macOS on the iPad this would be the next best thing. Imagine having Linux or macOS on the iPad that is treated like any other app (sans memory limits and etc.). You could have a full blown desktop at the ready when i
14.
by bwilliams 4y ago
I think this may miss the point of the article, which is pointing out that you can get a lot of value for very little effort by using a timestamp instead of a boolean. I don't think it's intention is to replace a complete change h
15.
by bwilliams 4y ago
The beauty (and horror) of Ruby is that you can do almost anything with it. I think this is a really interesting and clever use of the "can do anything" aspect of Ruby, although I think I'd prefer not to run into it in a prod
16.
by bwilliams 4y ago
I'd even be happy with a performant VM app that I could run linux on at this point. It would be so nice to be able to swipe up and go from linux VM -> imessage, etc.
17.
by bwilliams 5y ago
The advantages you listed are potential advantages but the reality is often different. Those features don't come for free, and given the number of SPA's out in the wild it's rare that functionality like offline mode or grac
18.
by bwilliams 5y ago
It's also worth mentioning the Enumerable module that can be mixed in to classes, which gives you `map`, `select`, and much more for free by implementing `each`. https://ruby-doc.org/core-3.0.2/Enumerable.html
19.
by bwilliams 5y ago
I don't disagree, and that lack of common interpretation can be both good and bad. Good because it lets you apply your own understanding and experiences to it, and bad because it introduces the potential for conflict when two people ha
20.
by bwilliams 5y ago
I read the article and didn't really feel that they disagreed with, or debunked any of the principles. It reads like they formed their own understanding of each principle and maybe disagreed with how they were taught, or how the princi
21.
by bwilliams 6y ago
Feels somewhat abandoned at times, but Apple Books is okay.
22.
by bwilliams 7y ago
> You can write something and be done with it, then move on to the next thing. That's part of the problem, you really can't. Requirements change. You have to update that service, and hope it's backwards compatible because
23.
by bwilliams 7y ago
I 100% agree it's all trade-offs. I think cost is important, but in that scenario it's going to cost them a lot more in time to split out and maintain several services. Devops was only one example. Their development speed will als
24.
by bwilliams 7y ago
Rewriting piecemeal is a great idea but extracting microservices adds a whole new set of problems that likely aren't worth the tradeoff, especially when your team is just you or only few other people. eg: Now your devops responsibiliti
25.
by bwilliams 7y ago
I've tried a few out like todoist, things, wunderlist, etc. and none of them really clicked with me despite my efforts. My new killer app is a tiny muji notebook and a decent quality pen or marker. I find it easier to remind myself to
26.
by bwilliams 8y ago
That's an option, but I can't imagine many folks would want to learn Delphi and continue to invest their time into it unless the money is worth it.
27.
by bwilliams 8y ago
If your API is down who cares if your app is being served or not? In the majority of cases it won’t work because the API is down.
28.
by bwilliams 8y ago
> A bug in one "page" of the app can cause the whole application server to go down. That doesn't seem like a valid issue. If a bug in a single page could take the application down then the same could be said for the API po
29.
by bwilliams 8y ago
> comments like these I strongly disagree specifically about comments like these throughout an active code base. A well named variable or method can act as a much better descriptor of what’s happening and doesn’t have the same maintenanc
30.
by bwilliams 8y ago
I think that’s fine as a choice for a personal project, especially since your committed to it. It’s a totally different story when working with a team though. Comments become outdated, files get larger, and it becomes more of a hassle to ma

More ›