Time to move off of Codeberg. They provide a service, that's it. I don't want drama from my service providers, and censorship incurs drama. I think some censorship is needed (hate speech, CP), but I do not want projects deleted because someone running the service doesn't like how I make them, or what they are for. They have the right to do that, but I also have the right to vote with my feet and go elsewhere, and I'm doing that. LLMs assisting coding has it's place, crypto has its place, both have been overhyped and so we're now getting a rubberband effect as people express hatred of these things based on the hype - not on their legitimate purposes.
The article makes sense for me.
I see it like the broken windows policy of software development. If you allow sloppiness in the small places, the places where you allow it will grow, until your code base is riddled with it. The fight for code quality is also a fight against damaging bugs and against exploitable vulnerabilities.
One big problem with the fight is that industry is incentivized to cut corners. '(Fast, Cheap, Good)..pick two' often results in managers picking fast and cheap. In some ways,they seem legally obligated to fast and cheap due to fiduciary responsibility to the stockholders. That's only if you look at the potential profit and risks from a very short term. Alas, that is what most of the world's businesses do at the moment. To paraphrase Dom from the Fast and the Furious, "We live our lives one business quarter at a time". Eventually Dom discovers the futility of that during the course of the series. Hopefully we will too, before we crash.
Bjarne Stroustrup said "C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off". The same is true of Rust macros. When you need them they're awesome, but you should almost never need them - add a new macro as a very last resort.
I used lit for a project a couple years ago, and loved it. It had some warts, mostly around working with React components and the Shadow DOM. But it's barebones IIRC. One of the things I loved about it was that it was focused on implementing and using WebComponents via the standard, rather than re-inventing all their own thing.
This brings back memories. I enjoyed following the travels described in the She's a Flight Risk series. I never did quite buy that it was a hoax either, though perhaps I am too gullible. If Isabella V. was real, then I hope she's chilling on a tropical beach in Buenos Aires, or somewhere else.
Great idea, and I'm looking forward to trying this out!
Each person with ADHD is affected a little differently, based on anecdotal evidence from family and friends. What are the available customization options?
I also do not see Google parting with something so critical to their advertising. With their own browser they control the full length of the wire between the ad-server and the user. Without it, they don't. Only way I could see this happening is if Google then released what they considered a better browser.
We've seen down that road. We know where it leads. Look at the imagined futures of games such as Shadowrun and Cyberpunk. This way lies an extreme dystopia for everyone except the ultra-rich.
I like this, but need more detail in my log and have too many things in a given day to have them all on a line. Had the following idea, and will try it out at some point. Call it calendar.md
Use calendar.txt format and method with the following changes:
1) Use markdown, with a top level heading of Calendar (so inclusion is easier) and the portion
2) Use :tag: instead of +tag. Tags can be run together (:tag:tag2:). This helps with Org mode compatibility
3) Third level heading for each event in day, following same format as calendar.txt
4) text under heading is for notes about the event
5) Searching and seeing info on event in day, or summary about day is no longer easy with grep. This is the biggest drawback from not using calendar.txt. Overcome by writing a tool mgrep that is specifically designed to search markdown files in a Markdown aware way (search headings or specific level of headings, show all headings under matching heading or just one level under, show all content under matching headings, search text and show either lines or section text is in optionally along with ancestry of headings).
6) Create CalendarMDMode, minor mode designed to facilitate calendar.md use and editing within Emacs, requires OrgMode, things like shortcuts for new date, new event, in-editor use of mgrep, etc.
A company can produce software that is two of fast to make, good, or cheap to make. A publicly traded company seems legally obligated to not choose good, because fiduciary responsibility is interpreted as what's good for short term gain.
I suspect this is because of a continuing rise in the percentage of home sales representing home purchase as an investment by an investor instead of purchase for habitation, but I have no citable research to back that up at the moment.
In your opinion, how far out are we from an AI agent that is usable as a daily driver (i.e., does not have the flaws in Operator, or other common flaws)?
I called myself a Semiotics Engineer for 4 years, but the title didn't catch. I did domain analysis, logical model creation, concrete model creation in XML/OWL/KML, model review and improvement, semantic reasoning-based system design/implementation, and message system design/implementation. This was before the rise of ML.
This is fascinating work and sounds a little like the research my daughter says she wants to study (she's only a sophomore at UMBC right now, though). She hopes to get an internship in the summer of her junior year. She is interested in plant biology and bioengineering.
If I understand correctly, plants have RNA - would this mean new RNA-based lifeforms could also be found within plants?
There was the Locker project by Jeremie Miller (XMPP), but it failed to gain traction and I think he pivoted into a more small scale commercial effort with it IIRC. The telehash protocol of Locker was extremely interesting.
Kudos for creating this. However, as others have said, the HTTP/1.1 protocol is most of what is needed.
I do think there is room for improvement though. Not in the conceptual or logical HTTP/1.1 protocol, but in the physical over-the-wire implementation. I'd like to see a version of HTTP/1.1 designed to work with CBORS as the main over-the-wire format, possibly including support for CBORS over COAP.