ekosz

Reading articles like this one, I do think people are trying to put a square peg (their applications) through a round hole (ATProto). The ATProto was designed around all data being public. You write public data to a user's PDS and then any application can read that public data and do something with it. If all data was private (encrypted?) by default then that would defeat half of all of ATProto's goals.

Imagine someone starts startup A on-top of the ATProto. They raise some money, get some users, some people love it, but ultimately they die. If the data was private to that service, that data dies with the startup. But if the data is all public future startup B can read that old data and do something with it. As a user that's brings me a ton of utility and comfort trying out new services.

If you're trying to built a local-first, mostly private service I just don't think the ATProto is the right tool for the job.

I think Hyperscript is easy to bash on due to it's _very_ different syntax than what programmers are normally used to. That said, I think it's a really nice way to add little pieces of functionality without needing to bring out the JS frameworks.

It should be remembered that Hyperscript is meant to be paired with a technology like HTMX. I don't think the creator of Hyperscript would be suggesting to anyone that someone attempt to create a web application out of pure Hyperscript.

I think that's a large thing to assume. That announcement could also have been easily just damage control before the markets opened on Monday and nothing has yet to be truly hashed out and agreed on.

Because if they wanted to keep their compute credits that they desperately need to achieve their mission, they cannot be randomly pissing off their biggest collaborators. Just because the board doesn't legally _need_ to work with their for-profit investors, doesn't mean they shouldn't.

Had they played this like adults they could have seen through a smooth transition and not be looking at a total collapse like they are now.

I think what people in this thread and others are trying to say is that to run a organization like OpenAI you need lots and lots funding. AI research is incredibly costly due to highly paid researchers and an ungodly amount of GPU resources. To put all current funding at risk by pissing off current investors and enterprise customers puts the whole mission of the organization at risk. That's where the perceived incompetence comes from no mater how good the intentions are.

Interesting to see oh this will affect (or not) the Rescript project.

We've been hearing complaints from AT&T users for months now that our website (https://vstream.com) doesn't work for them. I've tried hunting down the reasons & tried getting in touch with AT&T to no avail. This seems like it could be the very thing that's causing the issues for our users.

Now I just need to figure out what to tell our users that are having these issues...

You can try it yourself without any of the math with just a little bit of programming.

  function calc30(odds) {
    for (let i = 0; i < 30; i++) {
      if (Math.random() < odds) return true;
    }
    return false;
  }
  Array.from(Array(10000)).map(() => calc30(0.04)).filter(Boolean).length //=> 7022 or ~70%
  Array.from(Array(10000)).map(() => calc30(0.02)).filter(Boolean).length //=> 4545 or ~45%

Lattice | San Francisco, CA | Tech Lead, Software Engineer | Full Time | On-site

Lattice offers a performance management solution that helps companies put employees first. We offer 360 reviews, real-time feedback, weekly check-ins, and goal setting in a way that allows companies to focus on employee development, growth, and engagement. We launched in summer 2016 and have grown to over 800 customers around the world. Lattice has raised $9.8 million in total funding from Thrive Capital, Khosla Ventures, Y Combinator, Slack Fund, Marc Benioff, and others.

We are looking for product focused, full stack engineers to join our growing team. Our current stack is primarily React / Relay on the front-end and GraphQL / Node on the backend. You should be comfortable with both shipping products in JavaScript, and knowing when it’s not the right tool for the job.

Check our postings @ https://jobs.lever.co/latticehq/?team=Product

Lattice | Product Engineer (Fullstack or Frontend) | San Francisco | ONSITE, https://latticehq.com

Lattice is a performance management startup that helps companies track and improve employee performance. We believe that good performance management is critical for companies and employees to be successful. Unfortunately, the process is often painful, but we don't think it has to be that way.

We're growing really fast, based in San Francisco, and backed by some of the best investors including Thrive Capital, YC, Khosla, Marc Benioff, and Alexis Ohanian. The company was founded by myself (Eric Koslow) and our CEO Jack Altman. The engineering team only has four full time employees, so there's a tremendous opportunity to grow your career and have a big impact on a growing startup.

We use React on the frontend, NodeJS on the backend, and communicate over a GraphQL API. If you enjoying working with cutting edge technologies this is the place. We're looking for individuals that are product minded and enjoying owning problems from ideation to deployment. We have a very collaborative work environment and engineers work on all parts of the stack and across many domains.

If you're interested in the role, apply here: https://jobs.lever.co/latticehq/a29cefce-04ca-4a4e-86ba-9245...

San Francisco | Full Time | Onsite

Lattice is making performance management software for companies that put their employees first. Our mission is help companies run better by building great performance management software. We make it easy for companies to manage their goals and performance reviews.

We're a young company looking for ambitious engineers to help us build great product. With both user base and revenue increasing every month - all we need is you.

Our current stack is React / Redux / Relay on the front-end and GraphQL / Node on the backend. This role will focus primarily on the front end but ideally you’d also be comfortable working on all parts of the stack. While existing Javascript experience is highly desirable, we are truly looking for engineers who are passionate learners, willing to pick up whatever is necessary along the way.

https://boards.greenhouse.io/thesourcery/jobs/478290?gh_src=...

Great idea, I just opened up a PR for my project. Before this I had no idea how I was going to find a new maintainer and felt pretty guilty for moving on. Hopefully this gains some traction!

Hey lasryaric, sorry about that. Mobile signup is still a little weak and buggy. When you get a chance can you try going to your created account on your desktop? You should have an email from us with a link.

Hey everyone, I'm one of the co founders of Lattice with jackaltman. Really excited to be launching publicly today. We've already been working with some awesome companies helping them set and manage their goals and we're excited to get the chance to work with even more now.

If you have any questions about the service, please hit us up!

Hey harj! The article and plan is really interesting. I wanted to read more of the details and comparisons, but it seems the link from the sentence "We’ve created a summary of the gory details on both the business and legal aspects here" just brings you to the triplebyte homepage. Do you happen to have a direct link to that page?

This is a very cool library. Thanks for the link. Have you used this in any projects yet?

I remember Evan Koslow talked about this idea back in 2010. It was a pretty interesting lecture[1].

[1] - http://www.youtube.com/watch?feature=player_detailpage&v...

I remember Evan Koslow talking about[1] this back in 2010 at the University of Waterloo. Really thought provoking stuff.

[1]: http://www.youtube.com/watch?v=9RYXqCtsZsc&feature=playe...

I believe what he's talking about is that you do not NEED a DB for those features. One could implement authentication using a persistence mock. Eventually you will need to replace the mock with some sort of real persistence, but that is unrelated to that use case and should not affect the implementation.

I think the idea he is trying to express is that developers put too much focus on the persistence layer of an application too soon in the development. When you say I am going to use MySQL before you even write a line of code you are automatically trapping yourself and your thinking.

Persistence is meant to be an after thought of a use case; an implementation detail.

I'm not a low level programmer, but could someone tell me if you could write a LLVM backend for this CPU? If one does that, could it not then work with many programming languages that support LLVM?

http://llvm.org/docs/WritingAnLLVMBackend.html

I just got around to uploading this lecture my father gave at the University of Waterloo. My father, Evan Koslow, is a very successful serial entrepreneur who has started dozens of businesses. I've always found his teachings to be pretty educational and inspiring. Even though it isn't the best quality video, if you have the time I would give it a watch.

I uploaded a lecture my father gave at the University of Waterloo. He is a very successful serial entrepreneur who has started dozens of companies. Even though the video quality isn't the best, I thought HN might be interested in his very unique ability to 'invent at will'.

I completely agree, but I am also follow the school that you shouldn't spend energy on something you can't control or stop. Instead you should focus on things that you can readily change to mitigate the problem, or even make it go away.

Is that per year or for the whole degree? I was living in Waterloo and the students I talked to were paying $5-$15k a semester. To put that in perspective for an American, at RIT I was paying $40k a year + all of those living expenses.

I haven't worked on it in a while, but you can still view the code here: https://github.com/ekosz/Personal-C-Assistant

To get you started you might want to implement a Google Voice like application. Though that sounds that might sound difficult, using Twilio it can easily be done in a weekend. It will teach a lot about how to create Twilio applications plus it gives you the freedom that Google Voice lacks.

For example I hated getting phone calls when I was in meetings. So I hooked my Twilio app into my Google Calendar API and bam, when I was in meeting Twilio would ask them to leave a message or press 5 if it was an emergency. Also greeting people by name when they call is pretty awesome.

I wish I read the comments here first.

I can't seem to find a link to this in action. I just find two blog posts about it.