• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • The central point of that article is certinally valid. Something that was worked on for a while with broad congressional support and public support getting vetoed isnt ideal for a democratic process. No resolution on issues is not a good thing since another 3-6-12 months of no regulation for a theoretically netter bill to work through the system will allow for continued abuse by AI behemoths. Newsom is a corpo dem, so idk what people expected, anyway.

    I don’t buy into the AGI FUD. These are word calculators. But these tools are being hooked up to all sorts of things they shouldn’t be hooked up to and the lack of broad privacy regulation in the US puts LLM usage that handles sensitive data and/or decisions firmly into dangerous territory. Business decisions made by irresponsible management with no regard for data privacy or human safety are already a massive problem that actively cause harm, and hooking current AI tools onto these processes only seems to make the problems worse, especially while AI usage is in this gray space where no one wants to take responsibility for the outcomes.




  • Personal experience bias in mind: I feel like owners and managers are less interested in resolving tech debt now vs even 5 years ago… Business owners want to grow sales and customer base, they don’t want to hear about how the bad decisions made 3 years ago are making us slow, or how the short-term solution we compromised on last month means we can’t just magically scale the product tomorrow. They also don’t want to give us time to resolve those problems in order to move fast. It becomes a double-edged sword, and they try to use the “oh well when we hit this milestone we can hire more people to solve the tech debt”… But it doesn’t really work that way.

    Its also possible I’m more sensitive to the problem now that I’m in them lead/principal roles rather than senior roles. I put my foot down on tech debt a lot, but sometimes I can’t. Its a vicious cycle and it’ll only get worse the longer the tech sector is stuck in this investor-fueled forever-growth mindset.

    Too much “move fast and break things” from non-technical people, not enough “let’s build a solid foundation now to reap rewards later”. Its a prioritization of short term profits. And that means we, the engineers, often get stuck holding the bag of problems to solve. And if you care about your work, it becomes a point of frustration even if you try to view the job as just a job.






  • Manifest v3 extensions work in Firefox, too. Its just the new thing. Its way easier to build cross-browser extensions with, too. V3 is actually a good thing overall, as its led to a lot of extensions being available for Firefox when the devs might have just targeted chrome. Way more feature parity between browsers with v3.

    Chrome dropping support for v2 doesn’t merit a response from Firefox because nothing changes for Firefox users and they’re not going to drop support. Any one who actually cares (and they should) will move to Firefox on their own, so why waste advertising money on that? Eventually Firefox and any other browsers who want to allow stuff like ublock will probably have a way to do the same tasks in v3 (and the Firefox Dev team has said as much in blog posts for ages), then it’ll just be a feature that doesn’t work in chrome. V3 just simply doesn’t have the API that ublock uses in v2.

    There have been discussions for years in the w3c standards group about this whole shitshow and this is one the chrome team have basically refused to budge on despite all the other browser teams. Its honestlu a mirscle they delayed it as long as they have. This was originally supposed to happen at the start of 2023.

    Chrome is kinda like a country with a overrule veto vote at the UN when it comes to w3c working groups since they can just do whatever they want anyway, and nothing will change until they no longer have that power. That said, browser feature parity is at an all time high recently and its because all the browser teams are working together better than ever. There are just these hard limits chrome chooses to stick to.





  • 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.



  • 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.




  • The political aspect is especially true. The FOSS confusion is often similar to the communism confusion, especially when it comes to small-scale things.

    Take the concept of a neighborhood garden that no one is expected to pay money into, for instance. “Wait, so the people here who like gardening don’t expect me to pay or provide labor unless I’m able to? What do you mean i should take only according to my needs? What about Jimothy, he never helps but he takes way more than I do! What do you mean Jimothy contributes as he is able or in other ways? How can i trust everyone to be fair?”

    Take the money for goods/services exchange out of the equation and it can really throw people off.


  • I’ve been using florisboard for a few months now. You will have typos. Auto-correct for obvious things would be nice… once you install a dictionary its not awful, but the dictionary struggles with simple typos since it isnt usually taking rhe surrounding words into context of the misspelled word. I think the only dictionary i could get installed was from libreoffice? So could just be a lack of common mobile typos in the dataset.

    Florisboard does support things i actually used from gboard like a function row up top with undo/redo, activating voice options, and a clipboard with history. It also supports things like apps that support the autofill hints similarly to how itd pop up on gboard. Of all the foss options, it was the only one that had these modern expectations, so i also think its the best bet for a gboard alternative people will actually switch to. Anysoft and openboard are way too minimal (not a bad thing, just not what an avid gboard user is looking for)

    Swipe on floris is ok. It definitely triggers when you don’t want it on occasion. And the lack of autocorrect makes recovery miserable.

    I tried openboard too, but i could not get openboard to a reasonable size on the screen. Pixel 7 pro is fairly big… and i use the smallest text scaling… but even the smallest layout options put the top row out of reach of my thumbs.