As someone who used to run my own video sharing site in the 2000s, it's super cool seeing how videos can just render so quickly in my browser and be moved around.
1,051 karma · joined September 24, 2012
As someone who used to run my own video sharing site in the 2000s, it's super cool seeing how videos can just render so quickly in my browser and be moved around.
Are there places where it would be well-suited, but we don't really use it because the default is reaching for our public keys?
1. https://html.spec.whatwg.org/multipage/dom.html#the-innertex...
Here's an excerpt from a New Yorker article about the case:
> The judge, William Alsup, quickly tired of such distractions. “Despite the excellent quality of the lawyers here, I cannot trust what they say,” he announced in court. The documents he was being shown, he said, included “a lot of half-truth” and arguments that were “not quite accurate.” Alsup clearly thought that something unseemly had occurred, writing in one ruling that Levandowski had resigned from Waymo “under highly suspicious circumstances,” and that the “14,000-plus purloined files likely contain at least some trade secrets.” He also noted that “it would strain credulity to imagine that Levandowski plundered Waymo’s vault the way he did with no intent to make use of the downloaded trove.” Yet Alsup wasn’t sure if Waymo had demonstrated that any of its information had been used in an illegal manner. “If you can’t prove that Uber got these trade secrets, then maybe you’re in a world of trouble,” he told Waymo’s lawyers.
https://www.newyorker.com/magazine/2018/10/22/did-uber-steal...
Faced with a weak case, Google settled quietly for 0.33% of Uber's stock, which is no tiny amount, but definitely not a landmark settlement.
The more concerning part is that:
1. Google pursued Lewandowski with the help of federal prosecutors, using the threat of criminal trade secret charges and
2. He was essentially abandoned by both his former employer and his current employer. The former attacked him to punish him for wrongdoing and to set an example. Uber abandoned him because he became too risky now that he became a weak point that could be exploited in court.
This feels like too much leverage for a former employer to have, regardless of whether you were truly guilty or not. In fact, I think the outcome would have been similar had Lewandowski stolen nothing at all.
I work on a pretty front-end-intensive app (https://wanderlog.com) and it makes code reviews way easier, as you can see the change in context.
The gifs occasionally can go over the 10 MB cap that Gitlab allows, and in those cases I do a quick re-encode using Handbrake to a mp4 video.
Wanderlog is building tools to make leisure travel easier. We're a YC W19 graduate who's raised a seed round and looking to hire our second (non-founder) engineer. We've raised $1.5m, but aim to only hire one more engineer to keep our burn low.
We believe that travel makes us and the world better, and are trying to lower the bar to travel by bringing together all the information you need to travel in the best tool to organize your plans. Our product so far is a Google Docs for planning travel and sharing recommendations.
We’re an engineering and product-heavy team. A typical week’s work involves talking to users, prioritizing tasks on a kanban, designing on Figma, and building and shipping continuously. Harry and I have worked at Stripe, McKinsey, and Google and studied Computer Science at Yale. We've built profitable travel businesses in the past, and at Wanderlog, we try to take the best parts of each of the our past workplaces and bring them together.
We believe in work-life balance. We work regular hours, take time off as a team to eat lunch together (and even cook!), exercise, and enjoy time with friends and family. We love travel and believe it rejuvenates us and makes us better people, and have quarterly travel offsites where the goal is to just enjoy visiting a new place and use the tools we’ve built.
If you enjoy travel, and would love to make it easier for the rest of the world to do it, send us a note at founders@wanderlog.com! We’d love for you to join our team.
In addition, just communicating with everyone about shifts and managing the people-side was also a challenge, and there never felt to be super-specialized tools for this.
Accurate staffing seems like precisely the kind of problem that good data and modeling could solve. Good communication is something that good UI design could solve too. I'm excited to see how this works!
That being said, I think we at Wanderlog (W19) would've needed much longer to raise if not for a chance in person meeting at Demo Day.
We were encouraged to cold-pitch investors in person in the halls during breaks at Demo Day. For one of those pitches, I found an awesome investor who'd heard of us through a friend. While he'd thought there was a gap in travel planning tools before, this chance encounter gave me the chance to sell the company a lot more than we got from the super-brief Demo Day presentation. We had a handshake deal 3 days after that.
We wrote more about the lead-up to experience in our blog at https://wanderlog.com and my conclusion is: it's harder to forge that quick trust and connection anywhere other than in person.
That being said, I do realize we were very lucky. This change could be good for some companies and worse for others, as it rewards solid businesses more than charismatic pitchers. I'm looking forward to seeing the Demo Day pitches for this batch!
There really was (is?) no faster environment to get started with a single dynamic page that can submit a form and display data from a database. I don't have experience with the more recent frameworks, but I'm sure they're very mature now.
The conclusions from the article were:
> Creating the Flutter application only took approximately ⅓ of the time it took to create both native applications combined. This proves how much time you save by using cross-platform frameworks. Their Hot Reload functionality also sped up the development cycle a lot.
> I was able to create the Flutter app faster than the React Native app, but that’s because I had more experience with Flutter than with React Native. I also didn’t know how to manage state properly in the React Native. That’s why declare both Flutter and React Native the winners of this experiment.
For performance, Bram wrote:
> It’s obvious that the CPU-usage of the Flutter application is smaller than that of the React Native and Xamarin Forms applications, and that’s why I declare Flutter the winner of this experiment.
> In the second experiment it was concluded that the Flutter application was less taxing on the CPU than the React Native and Xamarin Forms applications. This doesn’t automatically prove that Flutter is more performant than React Native or Xamarin Forms.
> There are a lot of features that the Cocktailr app doesn’t have, like caching for example. That would reduce the amount of network requests that need to be made and would make the app more performant, meaning that it could lead to different results. I also only used CPU-usage as a performance indicator. I don’t have any data on the memory or battery consumption for example. These are also an important performance indicators.
We at Wanderlog (https://wanderlog.com) are using React Native largely because the ecosystem around it is a bit more mature than Flutter's at the moment. It's definitely saved us time vs. writing native code. We've definitely run into issues, and I think the main things we'd want to test as alternate performance indicators if we were choosing a framework again are:
1. How performant/easy-to-implement are long scrolling lists
2. How easy is it to animate the dimensions of Views that affect layouts of other views
3. How many libraries are there for things that will be dealt with native code? Dealing with the boundary with native code is always going to be tough
As the article says:
> Best case scenario is if the service is local-first in the first place. However, this may be a long way ahead and there are certain technical difficulties associated with such designs.
> I'm suggesting a data mirror app, that merely runs in background on client side and continuously/regularly sucks in and synchronizes backend data to the latest state.
Here are a few premises:
1. It's a fact that only a small portion of users care heavily about centralizing and truly owning their data
2. As such, it's reasonable for companies to not focus on exporting data. That's not how they get value out of their data
3. That being said, companies should at least not punish that small group of users for taking matters into their own hands
Scraping is our solution to this problem, and the least companies can do is allow well-behaved (rate-limited) scraping.
> Every founder goes through an identical process: downloading Microsoft Word, changing variables in a legal template, opening it in Preview, attaching their signature, and sending it over to the counterparty. Automate this process. Offer templates for common documents (company formation, SAFEs, etc). In time, you might become the store-of-record for company documents.
My friend was working on a product that does this called Formswift! I can upload a PDF, have it convert to a set of form fields, and email it out pretty quickly.
It's not the most glamorous-looking startup, but it works really well for the mom-and-pop small businesses that are their usual clientele.
Take a look: https://formswift.com/self-serve-builder
We wanted to store pictures of where the user wants to go and cache map tiles offline. Mobile Safari has a limit of 50 MB. This is not enough for these use-cases.
Even more annoyingly, Apple deletes PWA's on iPhones after a few weeks. Our users often plan their trips months or many weeks in advance, and don't look at them for weeks at a time. By the time they go on the trip, they may be shocked to see that Apple has evicted their data from the local storage, just as they land somewhere where they no longer have access to 3G data!
I think Google's approach of providing virtually unlimited permanent storage is also probably not the best, but something in the middle might be better.
At the moment, it's clear that making PWA's capable is not an Apple-wide priority, even if the WebKit or Safari team may be in favor. We decided to avoid fighting it and build a native (React Native) app instead.
If you're constantly ensuring that performance doesn't regress, this makes certain features a lot harder to implement. In some cases, the better solution is not to "make this feature take a lot less of the budget", but to say, "are there other parts of the budget that are easier to cut than the current feature".
Having regular performance optimization sprints allows for us to "cut where it's easiest" rather than forcing us to restrict non-performant features, when they might be very useful for the business.
Travelchime is building tools to make leisure travel easier. We're a YC W19 graduate who's looking to hire our second (non-founder) engineer and first designer.
We believe that travel makes us and the world better, and are trying to lower the bar to travel by bringing together all the information you need to travel in the best tool to organize your plans. Our product so far is a Google Docs for planning travel and sharing recommendations.
We’re an engineering and product-heavy team. A typical week’s work involves talking to users, prioritizing tasks on a kanban, designing on Figma, and building and shipping continuously. Harry and I have worked at Stripe, McKinsey, and Google and studied Computer Science at Yale. We've built profitable travel businesses in the past, and at Travelchime, we try to take the best parts of each of the our past workplaces and bring them together.
We believe in work-life balance. We work regular hours, take time off as a team to eat lunch together (and even cook!), exercise, and enjoy time with friends and family. We love travel and believe it rejuvenates us and makes us closer to our friends, and have quarterly travel offsites where the goal is to just enjoy visiting a new place and use the tools we’ve built.
If you enjoy travel, and would love to make it easier for the rest of the world to do it, send us a note at founders@travelchime.com! We’d love for you to join our team.
1. Just fork it and use your own version until the PR is accepted
2. Directly email the maintainer if you think your PR is worthwhile
3. If you have a bunch of PR's that are pretty useful to others, consider making it a real distributable (and not just a personal) fork if the maintainer still doesn't respond
> And I’m not aware of any maps that, for example, trace the safest sidewalks for neighborhoods in South L.A. or the northeast Valley—communities that have long lived with the kind of dangerous traffic that affluent neighborhoods, like the one where my family lives, now find unbearable.
While the author and I both agree that having safe neighbourhood traffic is good for local residents, it's an unfortunate property that only the rich have resources to do something about it.
The combination of Termiums's saved snippets and a short shell/node scripts let me do a lot of monitoring using simple shell scripts rather than having to run a separate web-server hidden behind some auth. Plus, it's still easier to build an interative shell script than an interactive webpage.
Travelchime is building tools to make leisure travel easier. We're a YC W19 graduate who's looking to hire our first (non-founder) engineer and first designer.
We believe that travel makes us and the world better, and are trying to lower the bar to travel by bringing together all the information you need to travel in the best tool to organize your plans. Our product so far is a Google Docs for planning travel and sharing recommendations.
We’re an engineering and product-heavy team. A typical week’s work involves talking to users, prioritizing tasks on a kanban, designing on Figma, and building and shipping continuously. Harry and I have worked at Stripe, McKinsey, and Google and studied Computer Science at Yale. We've built profitable travel businesses in the past, and at Travelchime, we try to take the best parts of each of the our past workplaces and bring them together.
We believe in work-life balance. We work regular hours, take time off as a team to eat lunch together (and even cook!), exercise, and enjoy time with friends and family. We love travel and believe it rejuvenates us and makes us better people, and have quarterly travel offsites where the goal is to just enjoy visiting a new place and use the tools we’ve built.
If you enjoy travel, and would love to make it easier for the rest of the world to do it, send us a note at founders@travelchime.com! We’d love for you to join our team.
1. Disclose the incident ASAP, even before all facts are known. The disclosure doesn't need to have any action items, and in this case, didn't
2. Add more details as investigation proceeds, even before it fully finishes to help clarify scope
The proactive communication and transparency could have downsides (causing undue panic), but I think these posts have presented a sense that they have it mostly under control. Of course, this is only possible because they, unlike some other companies, probably do have a good security team who caught this early.
I expect the next (or perhaps the 4th) post will be a fuller post-mortem from after the incident. This series of disclosures has given me more confidence in Stackoverflow than I had before!
Travelchime is building tools to make leisure travel easier. We're a YC W19 graduate who's looking to hire our first (non-founder) engineer and first designer.
We believe that travel makes us and the world better, and are trying to lower the bar to travel by bringing together all the information you need to travel in the best tool to organize your plans. Our product so far is a Google Docs for planning travel and sharing recommendations.
We’re an engineering and product-heavy team. A typical week’s work involves talking to users, prioritizing tasks on a kanban, designing on Figma, and building and shipping continuously. Harry and I have worked at Stripe, McKinsey, and Google and studied Computer Science at Yale. We've built profitable travel businesses in the past, and at Travelchime, we try to take the best parts of each of the our past workplaces and bring them together.
We believe in work-life balance. We work regular hours, take time off as a team to eat lunch together (and even cook!), exercise, and enjoy time with friends and family. We love travel and believe it rejuvenates us and makes us better people, and have quarterly travel offsites where the goal is to just enjoy visiting a new place and use the tools we’ve built.
If you enjoy travel, and would love to make it easier for the rest of the world to do it, send us a note at founders@travelchime.com! We’d love for you to join our team.
If you can line up a large number of them (through having worked in the Bay Area a lot, through your past employers), then you have a huge leg up that makes Demo Day less useful
People are very hesitant about nuclear power, but medical isotope manufacturing requires little enough nuclear fuel that it should be very safe. You sound like the right person to tackle this, and the market is definitely there. Good luck!
1. https://www.nature.com/news/reactor-shutdown-threatens-world...
- Works on mobile (like Quill, Prosemirror)
- Does not support collaborative editing (unlike Quill, Prosemirror)
- Has somewhat unique block-based editing UI - think Notion (the data models of most editors support this, but the default UI of editorjs is much more explicit about this)
- Not built on React (like Quill, Prosemirror, but unlike Slate and Draft)
The mobile support looks quite mature, and I think this could be a good competitor to Quill and Prosemirror for single-user editing.
Per my previous comments (1), I think for new projects, going with Prosemirror or Quill are still great choices. I've tried Draft and Slate and both of them have lacked good mobile support and collaborative editing.
1. As a first-time founder, YC (the community + the program itself) is a great education. I've learned a ton about different growth channels at a "growth bootcamp", about different possible business models (through the companies that have come and done talks and those in our small group), and about the pitfalls of a startup (through the former founders who are both in the batch and presenting at the talk). All of these have compressed a lot of informal learning into formal/less-informal lessons
2. You still get to choose how to run your company, unless you give up majority voting shares of your company and/or board control. Even that decision is ultimately up to you. It's important to go into every conversation having a good idea of what is best for you and your company, and then to consider what is best for the investor. You will face pressure, but it's essential to have your own perspective in mind and be steadfast in crucial circumstances
3. The community and credentialing is amazing. YC has a reputation that helps to hire and partner with other important companies and people
4. I put this last, but to some founders, this is the most important part. If you are raising money, Demo Day is just a completely unique circumstance to do it
I definitely don't regret doing YC, but I seriously considered not doing it before. I'd bootstrapped all of my past companies, but points 1 and 2 here were the ones my friends mentioned that convinced me to do it
We built a network-based (not UI/headless-browser-based) testing/scraping tool that was a bit like this at https://wrapapi.com back in the day, but the design on this new site looks really good