d0ntpan1c

Generally speaking I'm not opposed to sqlite. The case of a notes app is the one exception.

If i need to make a big find and replace change, i dont need to rely on the app to have the capability or whip out a sql editor or cli tool. I just open my favorite text editor and do it. Or chain some cli tools built into the os.

Its not even about data portability or export. Its about working with the data.

Exactly. Not a huge fan of notes apps storing the data in a db.otherwise there is a lot to like about joplin. With obsidian i open my notes in codium all the time to make mass edits or fill gaps that obsidians UI cant meet, which is not possible with joplin.

Fortunately with obsidian as long as you keep the plugins on the lighter side and keep any non-markdown content in seperate files via linking, im not too worried about having to jump ship if it ever goes bad. Worst case if a plugin dies or i have to migrate, the actual loss of data is that some plugin used json or whatever and it'd have to be converted or replaced.

I do have hope at least that if the company folds they'll open source it, or turn a blind eye to a community reengineering effort. And what is unique about obsidian markdown and metadata will probably get community-built migration tools quickly if enough people jump ship en masse.

But for the time being Obsidian is the best option for me and i dont feel that bad about it.

What drives me crazy about its programming responses is how awful the html it suggests is. Vast majority of its answers are inaccessible. If anything, a LLM should be able to process and reconcile the correct choices for semantic html better than a human... but it doesnt because its not trained on WIA-ARIA... its trained on random reddit and stack overflow results and packages those up in nice sounding words. And its not entirely that the training data wants to be inaccessible... a lot of it is just example code wothout any intent to be accessible anyway. Which is the problem. LLM's dont know what the context is for something presented as a minimal example vs something presented as an ideal solution, at least, not without careful training. These generalized models dont spend a lot of time on the tuned training for a particular task because that would counteract the "generalized" capabilities.

Sure, its annoying if it doesnt give a fully formed solution of some python or js or whatever to perform a task. Sometimes it'll go way overboard (it loves to tell you to extend js object methods with slight tweaks, rather than use built in methods, for instance, which is a really bad practice but will get the job done)

We already have a massive issue with inaccessible web sites and this tech is just pushing a bunch of people who may already be unaware of accessible html best practices to write even more inaccessible html, confidently.

But hey, thats what capitalism is good for right? Making money on half-baked promises and screwing over the disabled. they arent profitable, anyway.

I still use them since i got grandfathered into the pro plan (or whatever its called) without having to pay for a subscription. Not sure if i would pay for it now if i had to.

However, still a really good service for the cost to sync podcasts across lots of devices for anyone who listens to a lot.

Right, and then not watch YouTube or Netflix or anything on my.... TV... Good plan!

Roku was such an easy recommendation for a long time... Non-complex UI, long support for updates, not owned by google or amazon... Far cheaper than LG and Samsung... (Not that Samsung's UI is anywhere near as easy as roku)

But now I guess thats done. Unless an alternate firmware exists or this doesn't hit older TVs I guess I'll be looking for a new TV... Which is a shame because my current 4 year old roku TV is more than capable.

I picked up one of the ARZOPA ones and they are fine. Not the best looking, but good enough for a second monitor on the go. I used to take my ipad 9.7" with me places for this purpose and even though the image isnt as good, its way less effort to carry around.

I wouldnt use it as a single monitor regularly, nor for gaming.

I had to keep using the usb-c cable that came with it. Not sure if its a specific protocol that my thunderbolt 4 cables dont support or not. Minor inconvenience i havent looked into further.

Don't feed the troll.

Especially not one that uses mental illness as an insult.

I tried to use Copilot but it just kept getting in the way. The advanced autofill was nice sometimes, but its not like i'm making a list of countries or some mock data that often...

As far as generated code... especially with html/css/js frontend code it consistently output extremely inaccessible code. Which is baffling considering how straightforward the MDN, web.dev, and WCAG docs are. (Then again, LLMs cant really understand when an inaccessable pattern is used to demonstrate an onclick instead of a semantic a or to explain aria-* attributes...)

It was so bad so often that I dont use it much for languages I'm unfamiliar with either. If it puts out garbage where i'm an expert, i dont want to be responsible for it when I have no knowledge.

I might consider trying a LLM thats much more tuned to a single languge or purpose. I don't really see these generalized ones being popular long run, especially once the rose-tinted glasses come off.

Power users love to bash accessibility features like this. Its a classic case of "I don't need a wheelchair ramp so i dont know why the library added one!"

Accessibility is way more than screen readers. It's more than specific disability-minded modes. The web needs to be friendly to everyone, including people who may not know they could benefit from accessibility features. Everyone benefits from this type of work.

There are definitely some legit feature concerns and priorities being called out here. Mozilla has left a lot to be desired of late on that front. But a power user is more than capable of jumping into settings or about:config to turn things like this off, or finding an extension to get by for now.

Also the firefox dev team isn't tiny. This isn't blocking other work or anything in a substantial way, it's a fairly isolated piece of UI, and there's no guarantee that skipping this would change the timeline on anything else.

The page title isn't necessarily visible on the web page that sets the title.

Clicking is not always a simple task.

I shouldn't have to leave my current page just to figure out what another tab is.

Again, just because you feel something is useless or easily avoided doesn't mean that all internet users feel the same.

Tooltips are a standard accessibility feature. Just because you may not find them helpful doesn't mean others do not benefit. The delay is to ensure they don't get in the way unintentionally (but still allow usage) for those who do not need the accessibility benefit at all times.