HN user

vjeux

3,677 karma

http://blog.vjeux.com/

Posts35
Comments364
View on HN
skiplabs.io 1y ago

Skip – The Reactive Framework

vjeux
2pts1
www.fal.ai 2y ago

Real Time Sketching –> Image Generation

vjeux
9pts7
cpojer.net 5y ago

Rethinking JavaScript Infrastructure

vjeux
18pts0
engineering.fb.com 6y ago

Preventing Perf Regressions with Health Compass and Incident Tracker

vjeux
5pts0
github.com 6y ago

Show HN: Excalidraw – Sketch Hand-Drawn Like Diagrams

vjeux
30pts6
prettier.io 8y ago

Prettier 1.10: One Year of Prettier

vjeux
26pts0
writing.kemitchell.com 8y ago

The License Zero Manifesto

vjeux
190pts185
github.com 9y ago

Prettier 1.5: GraphQL, CSS-In-JS and JSON

vjeux
2pts0
github.com 9y ago

Prettier 1.4: TypeScript and CSS support

vjeux
7pts0
jlongster.com 9y ago

Prettier 1.0

vjeux
270pts76
medium.com 9y ago

Fast Source Map Generation for React Native

vjeux
17pts0
facebook.github.io 10y ago

Create React Apps with No Configuration

vjeux
777pts241
github.com 10y ago

Draft: Rich Text Editor Framework for React

vjeux
14pts0
github.com 10y ago

Show HN: Bot that mentions potential reviewers on pull requests

vjeux
72pts13
blog.freecodecamp.com 10y ago

We tried Slack

vjeux
3pts2
astexplorer.net 10y ago

JavaScript AST Explorer

vjeux
1pts0
github.com 10y ago

React Native Android Is Open Source

vjeux
5pts0
www.jamesaltucher.com 10y ago

What I Learned About Life After Interviewing 80 Highly Successful People

vjeux
3pts1
facebook.github.io 11y ago

React Community Round-up #22

vjeux
3pts0
facebook.github.io 12y ago

Jest – Painless JavaScript Testing

vjeux
168pts51
blog.vjeux.com 12y ago

Hack is to PHP what ES6 is to JavaScript

vjeux
10pts0
trac.webkit.org 12y ago

Apple Removes Shadow DOM from Safari

vjeux
90pts67
calendar.perfplanet.com 12y ago

React's Diff Algorithm

vjeux
143pts21
facebook.github.io 13y ago

React: Community Roundup #1

vjeux
6pts1
enki-tech.blogspot.fr 13y ago

C++11: A generic singleton

vjeux
25pts32
blog.pkh.me 14y ago

All the acronyms behind MPEG

vjeux
12pts3
fooo.fr 14y ago

Javascript Ray Tracer

vjeux
94pts25
www.adobe.com 14y ago

CSS Shader - Adobe brings WebGL to CSS

vjeux
62pts12
blog.vjeux.com 14y ago

URL Object Notation: A better JSON for URLs

vjeux
54pts57
github.com 14y ago

Experiment: Can we write a collaborative Javascript presentation?

vjeux
28pts5

I'm biased because I was part of the people that made it happen but yeah, I love React. Before that, I would try everything under the sun to fix the issues I was having doing front-end. But since React came out, I don't have this need anymore. I can just focus on building stuff.

We had the same issue many years ago with the reactiflux community. We ended up moving to discord and that was the best decision ever. Discord has been an extremely welcoming place for all these kind of communities.

Tldraw Computer 2 years ago

We actually intentionally round it to the nearest pixel in excalidraw because otherwise the font tends to be blurry. We may want to reconsider.

From my experience, the vast majority of reliability issues at Meta come from 3 areas:

- Code changes

- Configuration changes (this includes the equivalent of server topology changes like cloudformation, quota changes)

- Experimentation rollout changes

There has been issues that are external (like user behavior change for new year / world cup final, physical connection between datacenters being severed…) but they tend to be a lot less frequent.

All the 3 big buckets are tied to a single trackable change with an id so this leads to the ability to do those kind of automated root cause analysis at scale.

Now, Meta is mostly a closed loop where all the infra and product is controlled as one entity so those results may not be applicable outside.

excalidraw.com is a PWA, but not unsure how helpful it’s going to be as comparison. As mentioned in the comments, success is likely more due to the usefulness of the app rather than the tech used. vjeuxx@gmail.com if you wanna chat.

Meta Llama 3 2 years ago

The preview is using a different faster model so you're not going to get the exact same styles of responses from the larger slower one. If you have ideas on how to make the user experience better based on those constraints please let us know!

Meta AI 2 years ago

Thanks for the suggestion, will look into implementing it!

If I read the license correctly, it seems that if you want to use the LLM, you need to tell the authors what you are doing with it.

Am I reading this correctly? https://allenai.org/licenses/impact-mr

“Derivative Impact Reports. AI2 seeks to encourage transparency around Derivatives through the use of Derivative Impact Reports, available here. Before releasing a Model Derivative or Data Derivative, You will share with AI2 the intended use(s) of Your Derivative by completing a Derivative Impact Report or otherwise providing AI2 with substantially similar information in writing. You agree that AI2 may publish, post, or make available such information about Your Derivative for review by the general public.

You will use good faith efforts to be transparent about the intended use(s) of Your Derivatives by making the information freely available to others who may access or use Your Derivatives. You acknowledge that Derivative Impact Reports are not intended to penalize any good faith disclosures about Derivatives. Accordingly, if You initiate or participate in any lawsuit or other legal action against a Third Party based on information in such Third Party’s Derivative Impact Report, then this MR Agreement will terminate immediately as of the date such lawsuit or legal action is filed or commenced.”

Sorry for being late to the party. What I really care about is that we have fast code formatting in the industry.

But performance is a field that's really hard to accurately measure as there are so many variables, machines, benchmarks... You can see this in the JavaScript ecosystem where every project says that they are faster than the other one and they are in practice all right depending on which benchmarks they use.

So, creating a big bounty with something that's very hard to accurately measure is likely not going to work out very well.

In practice in the ecosystem, the Rust community really cares about performance. So it feels that this is the right audience to build something really fast. But, so far, none of the Rust-based printers were even close to outputting the same thing as prettier. They all decided to implement a different set of options, made different design decisions...

So every time somebody mentioned using one of those, I was getting annoyed that I would --love-- to recommend them, but it wasn't going to be the same. And I believe from experience that one of the main reason Prettier has been so successful is because of this --very very very very-- laborious last few percent of edge cases.

So goal #1 is to convince at least one of those projects to start being compatible with Prettier so that we had a viable alternative. In practice, there was no way I could talk to them directly and convince them to align with Prettier. So the idea of the bounty came to be, if I made a bounty big enough, it would be a way to convince them to do so (and it worked!).

The bounty to work needs to be very easy to test (percentage of tests that pass is very easy to test), cannot easily be cheated (unless you run prettier itself, you need to go through the laborious work of doing the same logic) and cover real world use case (all the tests were added over time based on using it in prod). It also mentioned a "project" and not a "person" to encourage collaboration.

It's a bit unorthodox but I've learned my lesson with code formatting that people are obsessed about discussing this topic so you need to find alternative ways to convince them.

Now, going back to Prettier, I've been very annoyed that nobody had looked at performance of the project since after I stopped working on the project. For example, I wrote a way to keep the prettier process alive for editor integration instead of paying for the startup cost every single time https://github.com/prettier/prettier-rpc and nobody used it. I needed to find a way to convince people that prettier's performance actually matters.

One of the most powerful way to get people to improve performance is to have two competing offerings battling against each others. We've seen this very successful between JS engines, JS frameworks... But, due to the success of prettier, there was no competition, the JS Survey admins even stopped asking about it because it was the only choice.

So having a proper competitor which is faster and uses a relatively controversial language, was a good setup to get a competition going. And it also worked, since the bounty was announced, Fabio Spampinato got nerd snipped thinking he can make the JS version faster than Rust and has been working every day profiling and rewriting the Prettier CLI to be orders of magnitude faster. We are using the open collective money to contract him to work on this.

Outside of performance, by having another group of people work on the same tests, they uncovered a lot of broken behaviors and edge cases on prettier that should be fixed.

Last but not least, having a bounty incentivizing another project was intriguing enough to generate a lot of discussion and therefore receive a lot more coverage than just asking people to work on your project.

----

So, overall, it achieved all the outcomes I wanted: by the end of the year, prettier itself is going to be a lot faster, and we actually have -less- fragmentation in the space where the other big project is now aligned in terms of the way code is formatted.

Would have I been able to spend $10k more effectively, I can't think of how. But I'm pretty sure I'm missing some better strats!

If you have points in a 2d space (a sheet of paper) and you want to separate them into two, you can draw a line between the two. The equation of a line is y = ax + b.

This is the equation of a neuron is you squint.

So if you chain a bunch of neurons, you are basically drawing a bunch of lines to test whether points belong or not.

With enough lines you can approximate any shape, like a circle.

What neural network do is given enough examples, it finds the lines that are needed to separate the points to give the appropriate label.

“ I’m sorry, but I can’t write code. But I can answer any questions you might have about BPE tokenization or any other text pre-processing techniques. Are you interested in natural language processing?”

Well this is unfortunate :(

I’m the maintainer of many high profile repositories in JavaScript land (react, react native, prettier, excalidraw…) and the following paragraph rings true:

“But there is no public evidence whatsoever that these instances warrant the noise, make-work, and consequent fatigue that their reports induce.”

All the vulnerabilities ever reported through this channel were regex dos and were absolutely not real security issues. Most of the times they were in code paths that were not actually used which makes matter worse.

Because a bunch of companies are hooking up their security processes with those reports, it leads to situations where people are alarmed about those non issues. It generates truly useless work to the maintainer and put them in situation where they have to justify that the report is completely bogus even though it has a “CVE” attached to it.

Eden 4 years ago

It was called css-layout but got renamed to Yoga because it implemented the “flexbox” layout and not all of CSS. Flex -> Yoga was indeed the joke/reference.