dsego

People can come and cut down trees, use the land for their cattle, raise crops or just start building something. If you don't challenge it and they get away with it for a while, they could even gain use of the land legally.

The public public land record in Croatia is notorious for being outdated and poorly maintained. Basically, the last time it was properly maintained was during Austria-Hungary a century ago, or at least that's the popular opinion. Right now we have the cadastre and the land registry and they do not always align. And for your example of unofficial agreements, the land my father and his brothers inherited is still in my grandfather's name, he died over 20 years ago, now my parents are aging, and there is just a verbal agreement on how the property is divided.

I remember copy/pasting scripts in dreamweaver to make leaves or snow fall on the webpage.

Yes, and now they don't have to agree, they ask an LLM, and we get half baked plans and quarterly goals and are left to figure it out ourselves. So the stakeholders have some ideas, some half assed designs get put together by an LLM, stories are generated by an LLM, technical details are filled in by an LLM, the implementation and code review are LLM. I can already notice the lack of critical thinking and scrutiny in the whole process, we're offloading all thinking and just creating these artifacts, designs, documentation, code, to what purpose I'm not sure. I'm having trouble even keeping up with everything going on. Of course, plans are more likely to change at any minute and we'll just rewrite everything on a whim.

People aren't forced to smoke, gamble, or drink alcohol.

It's one of those things were I feel like a frog in boiling water. Drivers need smart assists in cars because I see everybody is checking messages and scrolling on their devices while driving. The tech is solving things but also creating a need for more tech to solve new problems. A lot of things also remain unsolved from the earlier stages of tech. Eg. what happens to our digital lives when we die, can we have legal access so it doesn't rely solely on personal responsibility to share account keys and passwords. How is our digital life secured and backed up without having to come up with home grown solutions and be a sys admin or pay for cloud storage. Why can't we decide on standard protocols for messaging, we had SMS, now we have different messaging apps, people who aren't tech savvy lose years of correspondence when switching devices because they failed to import or transfer data. We still haven't solved data archiving to free us from bit rot and degradation, things like project silica are only in the research phases. All the while, we generate more and more data and make our lives completely dependent on digital services and devices. More and more bank branches are cashless now. We had a massive power grid outage a few years ago and at the convenience store we couldn't buy anything, there was no way to issue a paper receipt or anything like that, the store employees were clueless. I still remember a time when you could buy on tab/credit, they would just write it up, or at least take cache and issue handwritten receipts. And now we're piling AI on top of everything, but operating systems are still crap, software is mostly crap and we have to update our devices every few years because they become slow or stop working. And it feels like younger generations don't mind because it's the new normal, they grew up with smart devices.

Some of us even pledged to work ethically and practice integrity. Not sure what the original english version is. Found this online:

https://order-of-the-engineer.org/about-the-order/obligation...

Same here, I used a black power cord from an old stereo.

I get frustrated by this so much, because sometimes I come across a post with a video or something I want to see, but I leave it for a few minutes to take care of something, and then when I come back it auto reloads and I can't find it anymore, the back button won't work, scrolling through the timeline is futile, it's just gone.

Yes exactly, a democracy should be above markets. Not sure why such a strong reaction about people agreeing that certain things cause harm and should be legislated.

It's not just react, there is a lot of bloat included in modern interfaces, things like telemetry, metrics, error reporting, heatmaps, etc. React was inspired by PHP rendering exactly because it is a much simpler model then the usual two way data binding models.

It's very much a slot machine, maybe the next short video will be interesting. Maybe not, who knows, but you keep scrolling through shorts and binge watching.

So like Lit components or Stencil?

Everybody sort of settled on React and Node, or at least on the reactive/declarative component paradigm. React was introduced over 10 years ago now, it's a dinosaur.

It's not terms, it's structure. You all seem to be fighting calculus and saying knowing addition and multiplication is enough. I'm reminded of friends refusing to learn chords on guitar and trying to invent their own musicality so they are not constrained by music theory.

Really sorry to have to say this, but I feel like I'm getting underpaid for the work that I do if people make a living clobbering together input elements and calling it web development.

Svelte needs a build step, and with the introduction of runes for reactive state it's not that different from the rest of the crop (solid, react, vue).

I didn't mean rote memorization, which I agree is what other subjects were like, we used to say "campaign learning", because we studied the material just for the exams. But with math problems for me the trouble is that I didn't put in the work, I would see for example equations solved on the blackboard and it made perfect sense at the time, but because I would skip practicing at home, I would forget some of the steps and would get stuck.

It's like math in school. I wasn't good at math in school because I thought that understanding the concepts was enough. But without actually putting pen to paper and drilling through math problems you quickly get lost. It's a skill issue.

Are teleprompters a net positive achievement? They were needed for live television, they will be superseded I guess by AI generated news avatars. And 24-hour news coverage is in the business of generating content non-stop, to sell advertisements, regardless if there are newsworthy events or not, the machine never stops producing.

Rawtherapee, CameraBag Photo.

I share the sentiment, a lot of open source alternatives can't decide whether they want to be a replacement, a professional tool, a beginner user-friendly tool or just a playground for software devs. GIMP is awkwardly in the middle and has been stuck for a long time, it never met expectations, but became the default answer to any questions involving photoshop alternatives.

And it wasn't composable, state was kept in the DOM. Even with higher level libs like backbone we didn't have a component-oriented way like now. Each component had to manually manage all of its child components.

Eventually each crud form evolves into something more complex, the bar is set higher today, we expect pagination, filtering, search, inline editing, grids, instant validation, auto-save, push notifications, state sync, ... that's not a complex UI nowadays, it's expected. Not sure what a non-complex UI looks like.

But isn't that the right thing to do? Recognize the problems and introduce concepts to tackle them. C introduced pointers as a concept, one more thing to learn and reason about but frees you from using addresses directly. Relational models was discovered as a formal way of understanding and reasoning about data structures. Frontend components introduce a composable architecture with lifecycle hooks, reactivity etc. Those concepts were already there (e.g. with ad-hoc html templates, event listeners, clean up code) but now they are actually formalized and made explicit and developers actively think about them when doing frontend. So the abstraction is there, but I feel for some reason non-UI people assume UI is easy to code, but they never thought about the actual concepts involved. Even without frameworks, you need to consider composability, modularity, events, life cycle, state management, async behavior, etc. I'd rather have those built in and considered as part of the programming model, than to avoid it.

But it's harder to have component composition. Consider also lists and adding/removing items and so on, juggling all of it gets insanely complex and requires MVC or MVVM patterns like with backbone.js

We take for granted a lot of things, doesn't mean they meaningfully contribute to our lives, why is face tagging or thumbs up so special? I believe we already had upvotes and reactions on other platforms like early forums and chat platforms. Even if it was the first one to popularize it, it didn't really come about in a vacuum, the Web 2.0 at that time was all about user engagement and interactions.

I remember the 2000s web, it was primitive. It's not hard to combine some html and css, it is hard to support more complex dynamic actions and components, all with consistent theming and behaviors and have them composable and reusable.

It seems like you are throwing away the baby with the bathwater. I don't think providing 90% of the structure you need is a failed abstraction. And it just doesn't follow that it is pushing you towards sub-optimal structures, not sure where this conclusion comes from. All ORMs I've seen have ways to describe relations between models, even polymorphic types, aggregates, eager loading (to avoid N+1) etc.

But SQL is low level, eg. you can't dynamically pass in filters and construct statements without knowing what the query will be ahead of time. ORMs have query builders that allow you do dynamically construct SQL statement based on parameters, they allow avoiding N+1 queries by doing joins in memory and much more. It's just not possible with vanilla SQL unless you concatenate strings or have multiple versions of the same query for every situation. A good ORM is an abstraction layer above that gives you more powerful tools, it's like comparing high level OOP code vs machine code.