fezzez

If you look at their leadership. They have no one who knows how to code & understand's their core product at the helm. No one in their leadership team could use cypress themselves.

Decision like this come from the leadership team, and I don't think they have people with enough sense of what they're actually doing -- breaking trust with their end customers to understand this is terrible idea.

It smells a lot like what happened with Unity a few weeks ago. It's the same story. Leadership team weren't actually users of the product, they didn't understand that the company's key value was the trust they've built with the customers and they broke it.

This looks really convenient

Rainbow Insurance | Backend Engineers, Frontend Engineers (Senior & Staff) | 140k to 170k + equity | SF (onsite 2 days a week) | Full Time

We're a seed stage insurance technology company building insurance for small businesses. The team is small (just over 10 people), but experienced. We have folks with 20+ years of insurance expertise as well as a strong engineering culture from folks who've been working in fintech for decades. We're backed by top investors who've also invested in Asana, Vercel, and Brex.

Our Stack:

- React / Typescript Frontend

- GraphQL API

- Golang Backend

- On AWS

If you're interested reach out with a resume or a link to your linkedin at jobs@userainbow.com.

The story is that their founder made billions of a crypto trade a couple years ago so I think they might have the funding to do stuff like this.

Why does a link to an empty page have 24 upvotes?

I don't get it. What's the pun?

He had leverage. Facebook's massive growth meant that he could command the terms of the investment, and he ensured that he would always continue to control the board even as he was being diluted with later rounds.

If I remember correctly, I this was the original product Netlify started with.

Not new, but just been here the whole time.

Agree. The best way I can describe it, is that it's a design pattern for a lightweight runtime.

You can use monads to implement exception handling, global state (without actually having global state), and async/await.

It's difficult to explain how all those features can be implemented through one generic interface. But it's easy to see how each of those things would require a "lightweight" runtime.

Completely agree. That was my takeaway as well.

Similarly tried tan(x) and it crashed

Mosquitos are the closest thing to a predator that we have. They're by far the animal that kills the most humans (outside of other humans), and it's been that way for at least 10s of thousands of years.

We already know that billions of humans have genetic mutations that specifically are there to protect us from mosquitos. So I'm not surprised that mosquitos have specific adaptations made for us either.

How do you pronounce your name?

Didn't evervault get started on top of some open source work from a PhD student at Berkeley?

Can't remember what it was called but I think I remember seeing the repo on github

I gave it a try a while ago and it looked like their search results come from bing like duckduckgo.

Deep work by Cal Newport. It helped me learn how to be vastly more productive in the same amount of effort and time.

I was lucky to see have had this instructor for a couple of lessons. Bob is a total legend.

This is amazing! I had no idea the nyt paywall was all javascript.

It's to their detriment to do this. If this is on your Gmail, mark that email as spam. With enough people doing that, Comcast will either have to be more transparent about those emails or face the consequences of getting dinged by Gmail.

Not the original poster but I think the best answer to that would be from a talk DHH (the guy who made rails) gave about language choice.

He pointed out out that when he started his company there was no rails, or any great support for writing a server in ruby. He pointed out that it's actually surprisingly simple to get a barebones version of whatever library you like done in your preferred language. The original working version of rails was less than 2000 lines of code. Sure, there are no bells and whistles, but that's how rails started, and look where it is right now.

Compared to the ruby ecosystem in 2004, the Ocaml ecosystem actually pretty full of great libraries. Yeah, it's still tiny in comparison to the big server languages, but it's more than enough to build reliable systems on top of.

Not just that, but often researchers care more about building their CV than working on any specific company. A job is temporary, but the papers you write are forever. As a result, part of the reason why Google could even convince these people to work for them, is because Google cultivated this culture of allowing researchers to publish their research in most cases.

I think if Google didn't do that, it's possible these employee simply wouldn't have even decided to join the company.

I think you're in the wrong thread

Hey HN!

I'm one of the makers of Logfreely. We realized that most of the tools out there for managed logging we're hard to set up and had a pricing policy that quickly grew prohibitively expensive. We wanted to make a change to that and offer a solution somewhere in between self-hosting and a fully managed solution.

We manage everything: from provisions, to scaling, to version updates, but the servers and the data is ultimately on your cloud provider account. We believe this model better aligns incentives. We're compelled to find ways to cut costs for you, while at the same time you get to enjoy having full ownership of your logging stack.

We would love to hear your feedback and your experiences with logging. I'm personally excited to be sharing this with HN, and I'll be here to answer any and all questions you want to throw my way!

^To add to that. I'm doing exactly that to build this tool that lets you add logging statements onto running python without any restarts.

CPython gives you all the necessary utilities to let you freely manipulate pretty much any function's bytecode.

it's probably on github

Wow thanks for the kind words! I'm one of the makers. We still haven't found a solution for some of the problems that you've mentioned, but our focus from the start will be around privacy. I think you've grasped that problem yourself when you mentioned a self-hosted version.

On the technical side, we currently see this as something that can index on-the-fly, and maintain an internal representation of all the people who have the authorization needed to see the document.

I really like the idea of "auto-tagging". There's already research done on algorithms that generate tags from bodies of text. So it shouldn't be too difficult to integrate that into indexing.