Casperin

This is my preferred type of interface. Simple, fast, solid, to the point, and with shortcuts for (almost) everything.

... and I say that as someone whose day job for the past 7 or so years, has been building SPAs. Not all of us thinks tons of JS is the way to go.

Images are tricky. In the first few iterations, everything was left aligned and so images could just flow out and take all the space they needed. That was perfect for images, but less perfect for the reading experience. I'm torn. Sometimes I really dislike when other places cram big beautiful images down to their reading width; yet most of the time I'll agree with you--they should just flow with the text width.

I'll keep a mental note that someone actually took the time to suggest one thing over the other. Maybe it's the right solution. Maybe `max-width: 100%` with a click handler on the image that removes that, so you can toggle it up big if you want/need.

We could also make a simple "create test account for me", that will give you a few feeds, a dummy email and and dummy password. You can then just change everything later, if you feel like keeping the account. :)

Yeah, this seems to be the biggest complaint in all of this thread. We will do something to make it easier to get an impression of the reader for sure. I don't like screenshots, because, at least for me, the value is in the speed of navigating and the lack of surprises that a single page app will often give you (back button not working properly is the classic).

Cheers from Copenhagen :-)

I'm not sure what exactly your flow was here. Did you come from a specific feed? In that case the back button (ALT+Left) should work(?)

We will probably make the title of the feed within the post a link to the feed though. We can't have people getting lost like that. :)

Thanks for letting us know :) I think we found it in the logs, so we'll look into the error right away.

Yeah no prob. You can also change the email later if you need to. We aren't really that strict about it.

Oh that's cool. I stand corrected :)

It is literally as easy as login in. Just type an email address and a password twice and you are in. You can change your email address later if you need.

When you register, there is a suggested feed (xkcd) that you can add.

Yeah, I couldn't agree more. RSS is flawed in many ways (really difficult to work with sometimes hand-written XML), but I love how decentralized it is.

Awesome with your work! Keep fighting the good fight :)

Just put asdf@example.com (or something like that) and click register and you are in! We only use the email for retrieving forgotten passwords.

Yeah, we should totally do something like this if there is any real interest in this.

This post is to gauge that interest and it's our mini launch. (We are two beers into the celebration :)

Actually, to expand a bit on 3rd point. Whenever the internet sucks at work (I used to work in a bank where the VPN would sometimes crap out) I just go on weloverss and check my feeds. Those tiny payloads get through everything in no time.

Yeah sure. Here's a quick brain dump

* Faster page loads is the number one reason. It is super fast to navigate, once you get the shortcuts down. (For now it might actually be a bit slower if you're not in EU)

* Simpler architecture

* You get a lot for free by the browser (loading state, back button actually works, etc)

* Accessible

* Works on every browser (even your mother's potato phone :P)

* Works without JS

Yeah, Miniflux is definitely coming from the same mentality as we are. Also, it's great. :)

We love Atom feeds equally.

I can try. We haven't used Miniflux at all. We only tried it out a bit before we started working on our own.

* Miniflux is great. It's the closest to what we'd like.

* It is self-hosted and Open Source. Ours is not.

* It uses more JS than we do. And JS is required, I think (it's not in weloverss).

* Miniflux currently has more features than we do.

As for the business model. For now it's completely free because we just want to gauge interest. But the idea is to add a subscription fee in the future. We really don't like ads, so that seems to be our only good option.

I built this with a friend. We wanted a reader that is simple and fast and can be navigated using shortcuts, but isn't a single page application.

Sorry about not really showing anything before you sign up. It's very mvp right now. You can just use a throw-away email if you like :)

Is there any framework that explicitly allows me to set properties instead of just attributes? It doesn't play nice with web components when the object you passed in comes out as a string "[object Object]".

I will be the oldest person on the bench for sure (almost 40... time flies!), and I'm nervous as hell. :)

I will second Kragen in saying that there surely are many others like me, that has been inspired by your work.

Oh and btw, it was the post on Automata, not ripgrep. This one https://blog.burntsushi.net/transducers/

Burntsushi. Because of your blog post on ripgrep I found a love that I did not know I had (I am just a lowly self-taught frontend developer). I had no idea you could do magic like this with code, and that it could be that interesting. It made all the right wheels in my head spin and it was, and is, love.

I am going back to university (a place a swore never to return to) to learn about algorithms and algorithmic design, starting next Monday. Because of you.

Nobody has had this big an influence on my career, and every time I hit `rg` on my computer I do so with immense gratitude.

Just thought you should know.

This makes a lot of sense. It's essentially giving up some "niceness" that React gives to make it faster and closer to the metal. That sounds like a critique, but that's what this whole thread is about, and one way to approach something I've also given a lot of thought.

To do this, I imagine you will have to do certain things manually. I guess you can't just have functions that return a vdom, because, as you say, the absence of a property doesn't mean the library will delete it for you. So do you keep the previous vdom? Patch it manually and then send it off to update the elements? ... I guess it's a minor detail. Doesn't matter.

Interesting approach, thanks for sharing! I will definitely spend some time looking into it. Encouraging that it seems to be working out for you :)

I am sorry, but I don't fully understand. To me it sounds like you are describing exactly tree diffing when you say that the next node is only touched if its state object changed.

I have been through this struggle too. Of wanting to get rid of bloated tools and tools I don't understand, and the best I've found for this is Hyperapp. I've read the source code a few times (was thinking about patching it to work well with web components), so I feel it falls into a category of tools I can use. But I'm genuinely interested in understanding what you've done if it offers an alternative (even if more clunky).

As someone who's been doing frontend for 15+ years: I hear you. I wish the designers and PO's would hear you too. I am doing what I can to push back on these things, and so are every other frontender in my team. Keep giving this kind of feedback to websites if they ask for it. It's the best ammunition we have.

As a Dane, I'd say no problem.

Dane checking in here. On your last question, I'd say meetup.com for professional network, and if you enjoy any sports, join a club.

I had a friend from Spain who struggled for almost a year with socializing with us cold Scandinavians. That is, until she joined a Kendo club (is that what it is called? The bamboo sword thing). By the end of her two years here she didn't want to leave.

I haven't used KDE for 10 years or so, but what makes you prefer that over a tiling wm? Considering you were already there, the learning curve must be zero, and nobody is forcing you to spend any time modifying anything. It kind of just works. At least it does for me.

There are a very few things that I will drop into Gnome to do (I think it's Gnome at least), and I dread it every time. Too many menus everywhere, too much animation, tiny targets that I need to hit with the mouse, etc.

The first version was too long to fit on the screen for me. Reading the second I missed the swapping of `i` and `j` -- only noticing it when I went back to the first version to figure out which parts of line I would assign to something if I were to rewrite the code.

jQuery would have been fine, but honestly the website did not need that much js (if any). It should just have been a CRUD website.

Oh I'm so sorry, I didn't see the replies.

It was a mistake because we needed to move fast and figure out if we had something or not. A simple CRUD website (say Ruby on Rails, Elixir/Phoenix, or even straight up Node/Express) would have been faster to build and iterate on.

There was one section of it that would benefit from being able to work while offline, so that could perhaps have been built as a small SPA. But the rest, that was in hindsight a mistake.