1,062 karma · joined June 18, 2009
Ruby, and Ruby on Rails is a treasure trove of little handy bits you can use if you just know where to look. I really miss some aspects of ruby (I just don't have a chance to use it these days).
There is a big difference between a one time payment and a recurring payment, especially if the company canceling the product or going out of business means you can no longer use the tool, and I honestly steer clear of those in most cases.
If you get value out of the free part of a tool, great! If not, then you get to choose to pay for the rest or not. Personally I'm happy that it tends to be the feature set I can live without that costs money. Not always, but often enough.
It currently only runs in Firefox but if anyone is interested, I'll Port it to Chrome since it now supports a sidebar interface.
I made this because I wanted to have feeds show up where I read them, in the browser, and I wanted it on my own device so nobody else controls it. No hosting, no payment, just a simple tool that lets me control what I read.
Bonus: if you try it you'll likely increase the global usage by double digits ;)
I never really got where the innovation was in Arc, and never got a chance to see or try Dia, but the interview at least gave me some empathy for what they were going for.
The simplest example is if you have content that it not contained by the box you're positioning against. Think tooltips, popovers, etc.
For some usecases like annotating content, this hugely simplifies things.
If you want to have local first application data where a server is the authority, ElectricSQL is probably going to serve you best.
That said there are so many approaches out there right now, and they're all promising, but tricky.
English is weird.
I am a dev, and it took me a while to realize this was the pain point you were solving. Mayhaps I'm the wrong dev, and that's just fine, regardless this looks pretty neat.
And curses. Now I'm going down another rabbit hole rehashing ways to interface with my database in a side project that is doomed to never get past the "there has to be a better way to…" phase ;)
Is the goal of the project to let people write documentation for APIs, explore APIs, or something else?
Here are a few suggestions:
1. Start with a clear story of why you built this. Not lock in etc, but what were you or your team trying to do? That will help me understand whether I too try to do this thing.
2. Now you can tell me about all your frustrations, and I as a fellow misery drenched individual will say "Yes! I too have suffered the lack of cloud sync lock-in!"
3. Let me see it! Is there a way to embed the actual editor in the browser? Barring that putting a heading over the video, or a caption telling us what you're doing. When I click around to explore, let me click on those screenshots so I can see what you've built.
All in all, this looks really neat, but the challenge with building something divergent is that you need to invest more effort in telling the story.
I'm curious, do you output triggers, store procedures, and such? Many tools seem to stop after you've defined tables, columns, and indices, but I'd love some better tooling to make use of the rest of the DB's features.
I know there are services that offer more, but if I look at how I __actually__ used them, this does the trick.
On the other hand, I could imagine doing lazy migrations as user or tenants sign in as a nice way to smooth out the increased effort in migrating if you can engineer for it.
I think the maintainability comes from easy debugging. Stack traces are sensible and the code is straightforward. Look at a React stack trace and nothing in the trace will tell you much about _your_ code.
I'd also point out that this looks like it's about seven years old. We've shifted a lot of norms in that time.
I think this gives you slightly more control before interpolating.
If you want control flow inside a template, jinja and friends are probably still useful.
There's quite a bit of vitriol in the comments that seems overblown. There's a line where we're typing a few words in to get some AI slop out, but I think this is a long ways away from there.
On the other hand, asking useful questions can help prevent hallucinations or clarify tasks. If you're going spawn off an hour long task, asking a few questions first can make a huge difference.
Still appreciate the new features though.
https://gitlab.com/lecarore/breakout71/-/blob/main/app/src/m...
1. You will learn more, even when you think you know everything there is to know about the topic.
2. You can point to a thing you personally created. It's nice to be discussing a technical topic and be able to say, "Hey, I actually wrote an article about that, I'll send you the link."
3. AI might slurp up some of what you write, but it's a blurry filter over information. Your unique writing, details, and perspective are your own.
Finally, it can be fun or rewarding in the same way drawing, painting, or any other creative act can be. If it's not, then channel your effort into something else.
Super niche, mostly irrelevant to all but a vanishingly small number of people, and yet I had proof that someone I admired found it useful.
It's been years, and it still makes me smile when I think of it.
You never know what impact you might make on others.