3,028 karma · joined February 28, 2012
1. Organizing threads of research into context groups. Usually doing heavy deep dives where it’s uncertain if I need to revisit a previous branch, so rather than closing, it’s much more beneficial to group and collapse. It’s also easier to reopen and glance at the topics you looked at.
2. Similarly, grouping tabs by purpose while developing. It lets me organize tabs in a way that makes it so they I don’t need multiple browser windows open. It makes for a much more zen-like development environment.
3. Testing across dev, staging, and prod. Want the same tabs open but grouped so that I don’t accidentally do something destructive on prod that I meant to do locally. Now that this is in Firefox, I can also combine it with multi-account containers for more workflows.
Edit: that said, I think the majority of what the parent wrote is good. Esp the part about negativity. That hits hard and is good to be aware of.
If you can accept that you just happen to be born at the wrong time, you will be in a better place mentally than where I was at for a long time. I won’t say it’s easy; it will suck. But it is possible to make it out ok. I luckily had some financial and emotional support from my family to keep me going. I don’t know your situation but hopefully you are able to find support too. I wish you the best of luck.
Let’s do a thought experiment - If Google truly felt that Chromium has no benefit, then smaller players will drive the project and, as others have pointed out, new feature proposals/implementations will slow down. That isn’t a bad thing in my opinion because it allows other engines to not be stuck in catchup mode. The field will start to even out and innovations will start to come from alternative engines. With an even playing field, what was once an unprofitable endeavor can become a differentiator in the browser ecosystem.
- pushing for web ecosystem features that would help their own products (ex: Gmail, docs, etc)
- pushing for web enhancements that back SEO metrics that matter to them (ex: core web vitals)
I don’t think it’s as simple as - no more Chrome == no more investment into Chromium because Chrome/Chromium has been their strongest lever for getting web features that Google wants standardized. Stopping investment in that area cedes control of the web to other players who may have opposing goals to Google.
Possibly by trying to find a business model that can support Chrome development just like all other Chromium (and non-Chromium) based browsers?
As much as I loved Chrome when it first came out, I’ve also been well aware that Google’s backing of Chrome (and Chromium) has given it undue advantages in the browser market by effectively making everyone else compete with a loss leader. If Chrome itself cannot sustain its pace of development or even stay alive without the unlimited funding by Google, then I think that is a good thing and proof that it acting as a monopoly. Forcing Chrome to balance product velocity with revenue constraints evens the field amongst all browsers.
(edit: If Google killing competition by injecting unlimited funding into a project without needing to make a profit sounds familiar, it’s because they’ve done this for a long time. The often cited example being Google Reader.)
They won’t do this because then they can’t redirect any of the donations and funding that people give to Firefox to <insert non-browser project here>.
Quick summary:
- The original NYT library is this one: https://github.com/nytimes/react-prosemirror
- This is the author’s rewrite: https://github.com/handlewithcarecollective/react-prosemirro...
- They rewrote ProseMirror’s renderer in React instead of having a layer sit between the two.
- The author answered questions over on Reddit and had good insight into how their rewrite compares to other ProseMirror based libraries: https://old.reddit.com/r/reactjs/comments/1ij7lmb/why_i_rebu...
I'm not surprised that ChatGPT is being used this way. I used to teach ESL via the JET Programme and a lot of my job was about creating games and exercises that allowed students to get varied practice. I created or extended at least a hundred games in my 5 years there. These games weren't all successful, but the ones that were hit a cross section of:
1. repeatability (enabling pattern matching)
2. variation (just different enough to make it not mindless pattern matching)
3. difficulty curve (range of problems)
4. and fun.
As I learned the hobbies and personalities of all my students, I was able to get a higher success rate on 4. Being able to reuse games across multiple years helped me to fine tune 3. But nailing down 1 and 2 were always a challenge because of scale. A lot of times that was solved through instructors jumping in and adding new wrinkles on the spot. That worked well in the small schools I taught at (sometimes 3 of us for 20 students) but I don't think it would have worked as well in larger classrooms. I get the sense that using LLMs in creative ways has the potential to help solve the scaling problem.