dack

I am probably misunderstanding the article, but as far as I can tell, the two ways discussed are "JSON API like almost everybody does" and "do server-side rendering and call it the API".

Not to say it's wrong to do server-side rendering of the frontend, but I got the impression that the article wanted to make a distinction that I'm not seeing.

can't read the article because the site timed out.

maybe the code behind his blog is too clean!

This is true, but we also have to acknowledge that consistency is _fueled_ by something. Sometimes intensity helps us get over a psychological bump so that we see some initial progress and then want to keep going. So it's good advice, but it won't be that helpful if it assumes 100% self-control. Self-control is the hard part.

curious why it bothers you so much that someone else has a taxonomy? they didn't say you have to adhere to it. your opinion to just call all of it programming is fine too! but it's just an opinion

I can't tell how certain we are of its size - it's so big that it makes me wonder whether the easiest explanation is that our methods were incorrect.

For example, if we are measuring how light bends - how do we know there aren't many hidden (i.e. not large or bright enough to be noticed from earth) objects causing additional distortion and therefore throwing off our measurements? Do we also observe it over time to get more confidence, or have some other cross-checks that give us more certainty?

Either way, every once in a while I find it wild just how much we can deduce about the universe from our tiny fixed vantage point.

it was definitely a great place to work in it's heyday 10+ years ago, as I believe most of the FAANG companies were. It was so nice back in the day having companies you knew would be great if you could just get into them. Are there any companies like that these days?

I think AGI is going to be incredibly dangerous whether or not they open source their research.

I found that the missing piece for me was simply being kinder to myself when I slip up on some habit. Like, I tell myself "chill out - so you didn't go to the gym today. You're set back by one day. Just try it tomorrow." Maybe it's similar to your leaning into lack of consistency.

Previously I was so hard on myself when I made mistakes or wasn't up to my own (very high) standards, that I would quit after a while because it was a horrible experience.

Now, no matter how many mistakes I make, I don't beat myself up about it and I keep trying the next day. And I am seeing that not only am I getting more things done, but I am actually enjoying life more day-to-day, which is the ultimate goal imo.

how long have you been listening to it every day? I find that I do this with music but then burn out after a couple months and it doesn't hit the same unless I take a 5+ year break

Yeah I think the hype cycle with Clojure looks like this:

Stage 1: Confused by parens/the lispiness. early uncertainty

Stage 2: learn the REPL and library functions and fall in love. irrational exuberance

Stage 3: build an unmaintainable mess and can't refactor. trough of sorrow

Stage 4: figure out how to decouple appropriately and evolve the codebase rather than refactor all the time. live happily ever after!

The cljs stack I hear about a lot (and use) is ShadowCLJS with reagent (https://reagent-project.github.io/) and re-frame (https://day8.github.io/re-frame/). ShadowCLJS is more of a build tool, but is really well documented and easy to use. Reagent is basically react but a simpler API, and re-frame is a layer on top of that kinda like redux. It's overkill for some apps but I find it's actually super easy to work with and not as much complexity as I thought.

For backend there is luminus (https://luminusweb.com/) or Kit (https://kit-clj.github.io/). They are basically project templates that wire together a ton of popular solutions for various things - database access, migrations, security, html templating, etc. Also includes frontend frameworks like re-frame if you want.

edit: forgot to mention fulcro (https://fulcro.fulcrologic.com/) which is an interesting full stack solution. I haven't used it though so can't comment, but it sure seems documented well!

I don't quite understand why a client can't do it's own backup... it's really not that much data i would think. you could sync it to google drive or equivalent, and while your posts may temporarily be unavailable if all the relays are down, you could theoretically re-populate another relay (or your own) with that backed up data right?

creating and transforming immutable data structures can be a big pain in some languages though, and that's it's own barrier. java is a good example but it's getting better with record types etc

also worth noting: once you ship for yourself, you can update the app to work for more users. but it at least already works for one!

When you first hear a term used, I think it's natural for people just try to figure out what it means in context without looking up the official definition (I've caught myself doing this subconsciously before).

Imo a logical interpretation of "shadow ban" would be when you are banned but they didn't tell you they banned you, and regular "ban" is when they tell you you were banned. It makes enough sense that people don't think they need to look it up to confirm.

edit: funny enough, I did double-check the wikipedia page to make sure my understanding was correct, but upon reading further it does acknowledge the expanding of the definition: https://en.wikipedia.org/wiki/Shadow_banning

architecture diagrams change very infrequently, and are most useful in a given context (ie tailored to a particular viewer or team). writing actual code to describe them feels like a solution in search of a problem.

he suggested generating plantuml diagrams from it, so you would use the image for onboarding. you'd only see the code if you were going to update the architecture

I really like your framing of it!

To be fair though, I really haven't seen a change in the content on Twitter at all since Elon took over (modulo meta-discussion about Twitter itself). Time will tell I suppose

What do you think about giving individual users more power to moderate amongst themselves rather than having server admins do it? For example, a much more powerful "blocklist" type feature that you can share with others? So a could spend a bunch of time doing moderation, and publish a "blocklist" that other users could then install on their account so they don't see some set of people / content.

I agree with you that some users don't want to have to manually block specific accounts, but I don't agree that the network needs to decide. People already shared around "blocklists" for Twitter, and I understand there were even apps/browser extensions that helped with it. So yeah, you could say "I trust X person to make decisions about which accounts I see", without someone else also having to agree to that same set.

If such a feature was more robustly built into a platform like Twitter then the company themselves would have a lot less pressure in making a universal decision (which guarantees some disagree with)

I think some users liked Twitter exactly the way it was, so yeah, there was no need to change anything. Other users were literally blacklisted, or blocked from search, or banned. Or they wanted to follow such people and couldn't.

Yes, some of them were actual trolls or spammers, but many were just ideologically misaligned with Twitter the company (and/or their advertisers).

I think the problem to solve is how can we allow people to communicate AND DISCOVER other people's opinions without a particular company/organization making that decision for them.

Websites aren't good enough because they aren't very discoverable and don't have a robust discussion mechanism. I don't even think Mastodon allows this because admins seem pretty opinionated and end up cutting out chunks of the fediverse without the users' consent.

I'm not sure what the solution is but that is a real problem and it does seem necessary to "decentralize" to some extent as every group will always have conflicting opinions with other groups

what does "fresher" mean to you?

So happy for them! I hope they don't continue to work on the game forever because they feel bad for charging money. If it's genuinely what they want to keep doing, that's great, but they deserve to release more games (and charge for them!) if they want to. You don't have to toil away for 20 years to charge $30

yeah, it's purely a business decision, but it sucks.

Yeah that's super helpful for NixOS configuration options. What trips me up more is configuring particular packages. Usually it's where I want to configure a particular version or github commit of a package for some reason (usually I want a bug fix).

However, a bunch of packages are defined in some bespoke way with various custom config inputs that generate other bits of config and generally are hard to understand. Thinking it through, I'm not sure it's possible for the OP's tool to solve this particular problem.

Sounds great! I currently run a NixOS desktop but I still struggle quite a bit with the documentation and discoverability of configuration/language. That's one of the biggest pain points in my eyes, so a UI like you have could really make that simpler. Letting users introspect what settings are available and how they work seems like one way of making things more discoverable (but not necessarily making a specific wizard for a specific build, since that doesn't seem scalable or generalizable).

That said, I also agree with you that having reusable modules that are documented would help, and being able to clone and copy/paste settings + seeing examples would too. Good luck!

This looks really cool, but at first glance it seems like you really need to already know how to create nix flakes and what all the settings mean to use the site. I didn't sign up, but I watched your redis video (https://www.youtube.com/watch?v=3fuCGXHw7qM) and it seems like you just knew all the configuration settings you wanted and searched for them.

Maybe that's fine for your target user, but I would think you could get non-nix folks on board if there was more of a "wizard" type flow that tells you the options and explains them as you go through it.

agreed, I think this trap is related to fear of failure. if you're not telling people your plans because you're worried you won't finish, that might be bad. but then you don't want to take any credit for simply making me g plans either. maybe better to discuss what you have done _so far_ toward your goal

To be fair, for a while they were ALSO working on their own graphical source editor that allowed for type-correct transformations and assisted refactorings. They put that on the back burner specifically because they are trying to focus on fewer things :)

I think the distributed computing problem is pretty related once you have "content-addressable" source code. Agreed that it's a lot of work but I hope it pans out!

I think it's signaling that it's probably modern, fast, and that the authors care about correctness. I think the customer has to have bought-in to the Rust hype for that to work, but since it's a developer tool, I can see how it might attract some.