• 0 posts
  • 19 comments
Joined 3 years ago
Cake day: June 30th, 2023
  • Not to defend them or completely dismiss their part in all that, pretty sure it was just someone else sending the fiverr video to them and them opening it while streaming. But the latter incident, where they shouted some slurs on air while playing some game, that’s I think more inexcusable. But I always got the impression they never were actual nazi or far right despite the subject matter of the incidents, it’s more just them being an idiot and trying to be funny and edgy for content and missing the target entirely on a couple of occasions. I think the aftermath speaks for itself, they did some reflecting and ended up changing the formula and content type entirely, and we are now seeing the fruits of that effort.

    I don’t mean to belittle the shit they’ve pulled, but I also don’t want to paint anyone irredeemable, even less when they actually manage to do introspection and change. We should encourage that and highlight that instead. I’d reserve the unconditional hate and spite for those that deserve it, that don’t change, don’t reflect, perhaps actually mean the things they do and say, with passion.

  • Yeah doesn’t sound like vibe coding if you actually go through the necessary dances anyway, i.e double-check the produced code and validate it and actually understand it and the domain.

    Edit: But almost nobody does. Because then you’d rather just write it yourself and save time, money and energy…

  • Sorry, I go on tangents and end up just confusing people. It is! That was my point, though failed to deliver it. Gpl3, agpl and apache.

    They do have a pricing model for enterprises with some proprietary extra stuff on top (shared billing, SSO, premium support and stuff like that), and a tier for expanded AI stuff (entirely ignorable, and the editor works with pretty much everything, so if you need those things, you can just set up whichever service you want yourself), but those can both be ignored, the main editor is FOSS and committed to remain so.

  • I believe zed has extensions for c#, and I guess more importantly, dotnet.

    At this point, unless you have the money to grab sublime (or specifically want foss or even just free as in beer), and you aren’t sold on the way of life of the old guard like the modern vims or emacs, zed is pretty much the best there is.

    I used to be such a jetbrains guy, but that was back when they did actually have something nobody else really offered outside of Microsoft. Before that, for a good long time, I was an emacs guy, until I had to use a windows computer for work and emacs just doesn’t fit well there, couldn’t get a good equivalent of the daemon going consistently, had to switch. And to be frank, lisp is the fucking worst.

    Nowadays, there are so many options though, even, or especially, on foss side. Or even just free. Hard to justify the jetbrains kinds of specialized tools, now that the same sugary, smooth experience is almost exactly achievable on those. And faster.

    I have been happy with zed for quite a while now. Apart from the (disableable, thank god) first class AI stuff, I haven’t a single complaint. It feels as fast and responsive as sublime, and while the ecosystem isn’t there yet, I can get all my stacks and tooling to run currently like it was a jetbrains ide from back in the day. Rust, dotnet, deno/ts, it all just works after setup.

    I would still go for sublime just for the ecosystem, but I haven’t the economics at a point where I can choose convenience for a price, if a close equivalent exists with the price of nothing but contributions occasionally. The zed source being open, even if my PRs don’t get merged, I can just live with my fork and have it natively the way I want, without working around the extension limitations.

  • Then you’d need to do something else.

    Precisely my point.

    And I’m not advocating for any of that. That’s just weird design, both of them, and as such a good example of something that warrants a bigger redesign in general.

    Just advocating for clear, sensible, self-documenting and most importantly, expandable and maintainable code.

    What’s idiomatic varies between languages and the conventions aren’t the same even then, when arguing across disciplines. This discussion seems to be more about different educations. I can get your point but from my personal experience in academia and working in the field it sounds undesired. But that’s just it. My, as in extremely limited, perspective. From your pov what you argue here is probably equally correct to what I think from mine is from my pov, it’s just a difference in the segment of the field we work in I suppose. Or plain old cultural differences.

    Whichever it is, I bet we both can find better use for our time. I’m thankful for the time and effort though, even if I wasn’t persuaded. Sorry to have prolonged it so.

  • That is all just external implementation details. Not sure if it was you or someone else, but the main argument in defense of the OP as in it reasonable, was that the name is wrong. That it ought to be idAdmin. None of what you just described should have anything to do with user being or not being an admin. In place of checking “isAdmin” for null, the semantical and resourcewise equivalent would be a third variable for “admin rights having been validated” or whatever. Conflating it in this one variable while renaming it to isAdmin or similar, would be even less sensical… what if somewhere else in the code you have to check whether the initial validations have been made (while the actual role or whether is admin or not is irrelevant), you’d have to check if isAdmin equals null, which in that context would be confusing, ambiguous (i.e someone reading that bit will not know this is what is being checked without additional documentation) and just a code smell in general. You do want to make the important things unambiguous and self-documenting. Even more so the bigger the codebase is and the more contributors there are across its lifetime and in parallel at any given time.

    But if we go with the original meaning of roles overall, then the union type is just a code smell that warrants a proper role thing around it.

  • That all is besides the point. There’s no real advantage to use null instead of defaulting to false there… it’s semantically more accurate and also less wasteful in that other code does not have to worry about nulls which always leads to unnecessary overhead when false is already equivalent in your proposed example.

  • I don’t really follow you there, wouldn’t it be exactly the opposite and wouldn’t checking for nulls be, as a premise, more wasteful? But doesn’t really matter, time to digress. I’m conventionally educated as an engineer so what I know and find reasonable today might be outdated and too strict for most contemporary stuff.

  • Yeah obviously with constants for the set roles per value. Some languages call them enums, but the point is that what we pass and use is always still the smallest integer type possible. With the extra bonus that if the roles ever become composable, the same value type would likely suffice for a bitflag and only thing needing refactoring would be bitshifting the constants.

    But anyway, this turns out to be the weirdest hill I find myself willing to die on.

  • Yeah, but if it is about being an admin or not, hence the bool, it’d be idiomatic and reasonable to assume it to be false if we have no data. Unless we want to try and allow admin access based on no data. Having three states for a simple binary state is weird. And if it is not about just being an admin or not, the bool is inherently a too limited choice for representation.

  • Admin is a role though, was my point. And besides, if you check for three different states, and you decide to go with a boolean to represent that, I really find it hard to believe anyone would think it reasonable. It’s valid and it’s practical, but can you really say it’s reasonable?

    I don’t do typescript, but wouldn’t a union of a null and a bool be just more resource intensive than simply using an unsigned byte-sized integer? I struggle to find reasons to ever go for that over something more reasonable and appropriate for what it attempts to represent (3 distinct states as it stands, and likely in future more than just 3 when they have a need for more granularity, as you’d often do with anything you’d need an admin role distinction in the first place), but likely I’m just not familiar with ts conventions. Happy to hear the reasoning for this though.

  • Yeah let’s use a union of a boolean and null to represent role, something that inherently represents more than two (…or three, I guess) different values, as opposed to something like an integer.

    Even if the name is clearly misleading in this specific case, the entire choice of using a bool here is just bad because it’s almost guaranteed you’re going to expand on that in future and then you’ll just have to entirely rewrite the logic because it simply can’t accommodate more than two values (or three with the null union… 🙈), while it gives absolute zero benefits over using something more reasonable like an integer to represent the roles, or in this case, admin, not-admin and guest. Even if you’ll end up with just admin, non-admin and guest, the integer would still work great with no disadvantages in terms of amount of code or whatever. Just increased legibility and semantical accuracy.

    Not to mention that there’s zero reason to combine the state of being logged in and the role in which you’re logged in in one variable… those are two different things. They will remain two different things in future too…

    I mean they’re already chaining elseifs (basically matching/switching, while doing it in an inefficient way to boot 🥴) as though there were an n amount of possible states. Why not just make it make sense from the start instead of whatever the hell this is?

  • Huh. This has to be the worst promo site I’ve ever read. Whatever you described here does not seem to be reflected on that notion page.

    You are very clearly selling something, so obviously this is a bad post to begin with, but in an attempt to make fun of the substance itself, I found none that is coherent. Can’t even joke about this, it’s so goofy.

    Edit: I mean come on, what is this even

    Not all digital products are built to protect and perform.

    ZOKO is built to do both with zero theory, zero fluff, and zero BS.

    🧠 You get:

    • Real income systems tested in global markets
    • Scam-prevention + gov-supported survival strategies
    • Multilingual-ready, instantly applicable info
    • Verified insights from field execution (not guesswork)

    No vague advice. No bloated nonsense.

    Just pure tools to earn smarter and safer, anywhere.

    “No vague advice”, aye…

    Edit2: This is actually pretty funny

    • Built for clarity, not gimmicks.

    ✅ You’re not buying ideas. You’re buying results.

  • There’s Pixelfed, something of a fediverse Instagram. In many ways it’s actually better, even. But it’s pretty mature at this point and has a bunch of QoL stuff going on, such as mastodon signup/login thing.

    Unfortunately I think ig crowd is much less likely to move on to fediverse alternatives than Twitter or reddit folks.

    Hard to just quit ig for me too, when I have brand accounts to keep up and active, and it’s also actually the last social media I have family members and relatives on, and only thing allowing me to move would be for them to join fediverse somewhere, not necessarily pixelfed, but thats unlikely to happen very soon.

  • I think they made their bed, and I’m fully okay with them sleeping in it.

    Even if they roll back everything and I’d be the only one not sleeping in it with them, I’d pass.

    I’ve noticed this change has also been good for my overall mental health.