d0m

Highly recommend going outside, maybe hiking for a day.

What I liked the most was the "reverse-playlist search". For instance, if you find a song you like, you can see all the public playlists containing it. I much prefer that to the "let me recommend you songs" approach.

That's amazing, congrats for the launch.

From my memory as a kid.. I remember winamp was amazing. I had many skins and it was all beautifully hooked up in my IRC client.

And then, at some points, the UX completely changed. It also started being spammy. Almost like the project was sold to some incompetent people. Then I felt like it lost its magic. It also happened to be the time when streaming from Napster became possible and I completely switched to it.. and then to grooveshark/deezer/all-the-others.

Winamp could have been Spotify but went in a completely different directions. Saying that may sound crazy, but that's what Netflix did. It was selling/renting dvd, saw streaming coming and did a full 180.

Users of every startups: You have a typo

Founders: Thanks

Users of Hey/Basecamp: You have a typo

Founders: No, this isn't a typo. And we built a website to show you're wrong: http://itsnotatypo.com

Mobile web app should feel native; now they're slow, clunky, don't have access to important OS features

Thanks, english isn't my native language so I appreciate the help

From someone who hasn't learned/considered Go for any real project so far, would there be any benefits in going Go instead of Rust? Or learning Go instead of Rust?

The way I look at it, and I could totally be wrong, is if you go for a different language for your back-end than your front-end, it betters pay off big time. I find Go and Typescript to be in a very similar ballpark in term of productivity, but with Typescript having a huge advantage since you can reuse all the learning/tooling from the front-end.

Rust on the other hand really adds something to the table with the memory safety and zero-cost abstraction.

TL&DR: It feels like either you eat the bullet and go Rust for memory safety, or Typescript is a better choice. Of course I'm overly simplifying.

Thoughts?

Analogy: Like looking at stock prices. As javascript developers, we see all the tiny changes every day and it can feel overwhelming. However, looking at with a long-term view, there are only a few major spikes and it seems to be nicely growing.

not available in all js runtime

It's cool that anything sounds great

I'm curious as to how it works to develop on it locally vs a stage server & vs prod? I.e. how to make sure the workflows are synched and are easy to reason about?

Analogy: A bit like your boss. They shouldn't micro-manage your work, but they can fire/replace you if you're not good at it.

Quick shout-out toAptible (Heroku for HIPAA) which have been amazing for our healthcare startup.

Still, I honestly feel that we've taken a step back in the industry where we went from ec2 --> heroku --> k8s. But I know there are many people working hard to create the next infrastructure so we don't have to deal with containers and all that re-inventing dev-ops non-sense for every project.

Agreed, this is a great resource for developers wanting to improve their design skills. I.e. going from zero to "more-than-good-enough"

People use "boring" in opposition to "hyped" or "trendy", which like you said totally misses the point. I jumped on react right away when it came out, but not because of it being trendy, but because like you said I could be productive with it right way, I knew it'd be around for 5+ years and that I could hire engineers.

I remember when I was a kid I tried for days to install gentoo and it just was not working. After so many hours of banging my head against the wall, I realized the CD was corrupted. Re-burning the iso fixed it

Ha, that's a great term for it

IMHO this "almost open-source" is even better because otherwise people wouldn't be willing to start companies around their open-source solutions knowing that AWS would just offer a hosted version and screw them over.

>> By hosted, we mean charging customers for the hosted version of the open source product. The risk is that a cloud provider decides to compete with your hosted version.

An interesting approach is what cockroachdb did, which basically forbid this very specific use case, and is otherwise standard open-source.

I think the best way to filter/monitor social medias would be to:

A) Keep the core platform as open as possible, almost like a protocol (I.e. http doesn't care who says what.)

B) Build/invest in community-driven monitoring tools that users can select to filter the content.

works goes into "repo/<project name>"

personal stuff go into: ~/files, then ~/files/archived, then ~/files/archived/archived. At some point I just make sure it's backed up, delete it all and start fresh with ~/files.

Yeah, but it's a relatively low investment and you often just need one idea that works to pay for all the crappy ones

Yeah, please do share. Congrats on the pivot and Satchel looks pretty cool, good luck (Even though I'm not sure I understand the business model, I see a lot of value in the product)

I'm a big PG fan but to be honest, him building viaweb in Lisp is 99% because: "Robert and I both knew Lisp well, and we couldn't see any reason not to trust our instincts and go with Lisp.", and not because of a competitive advantage in the language.

There are so many things that can go wrong in a startup, it's not the time to pick a stack or database you know nothing about.

That bit was interesting:

>> Manually convert a list of ~100 commonly edited files from Coffeescript to TypeScript.

Seems obvious, but outlining it as a critical step probably helped in many ways.

Might be interesting to do a few hours of pair programming too; i.e. implement and ship a small feature

I guess the idea is that once you try doordash, you'll want to stay there because you have more choices and better product. Doordash can control the whole experience as well as send you emails, push notifications, etc. to bring you back in.

That's interesting, mind elaborating on this? How is the next version of Arc going to help with pagination? Is this a memory limit thing?