Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shaneos
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
shaneos
3y ago
It can be made work. Precompute the image when the flood fill tool is activated and it’s fine, since you only have to do it once
62.
▲
by
shaneos
3y ago
Author here: in the app I use that, it seems to help alright
63.
▲
Instant flood fill with HTML Canvas
(shaneosullivan.wordpress.com)
251 points
by
shaneos
3y ago
|
122 comments
64.
▲
by
shaneos
3y ago
Yes, this is correct. All the canvas stuff has nothing to do with React, so I bundle it all separately. In fact, I don't even load React on the browser, I just render the initial page with it on the server then just work with the DOM
65.
▲
by
shaneos
3y ago
Glad you like it :-). I'm planning to write a few blog posts about how it's built, there's some fun stuff in there - the first one will probably be about how I make the paint bucket fill operation be instantaneous, that was a
66.
▲
by
shaneos
3y ago
Yes, Bun is very much in beta, but it's already really, really good. I'm fine using it with my hobby projects right now, but once it gets to 1.0 I'll give serious consideration to using it in production code too. The API is
67.
▲
by
shaneos
3y ago
It’s the project I integrated Bun with as a bundler, thereby running into all these issues. I figured that others would hit the same problems so write this post about how to work around them
68.
▲
by
shaneos
3y ago
Glad to hear it! My kids love it which keeps me working on it. Having your ideal testers living with you is an amazing plus :-)
69.
▲
Using Bun.js as a Bundler
(shaneosullivan.wordpress.com)
137 points
by
shaneos
3y ago
|
42 comments
70.
▲
by
shaneos
4y ago
The example in the README seems to be dividing “undefined” by 1000. Am I misunderstanding something, does that code truly generate the output shown somehow?
71.
▲
by
shaneos
4y ago
Another shameless plug - I built a multiplayer sudoku game where you and multiple others can compete to finish the game first. It's a web app at https://countdoku.app/
72.
▲
by
shaneos
4y ago
Reading the docs, there seems to be a large amount of magical component creation going on that I find difficult to read. A key benefit of React is the simplicity of a component accepting props and using them in its render function. This lib
73.
▲
by
shaneos
4y ago
This is very accurate. I’m Irish, and when my Korean wife and I were leaving the US with our two young kids, Korea wasn’t even considered as a place to raise them. She had such a needlessly tough time as a kid, and her siblings are having t
74.
▲
by
shaneos
4y ago
Given Mudge's stellar professional history, and having worked near (not with) him for a short while, I certainly would take his word over the current Twitter leadership.
75.
▲
by
shaneos
4y ago
I remember you well!! I think my app Mazer came in second in the free category. Such happy, simpler times https://appcatalog.webosarchive.com/showMuseumDetails.php?se...
76.
▲
by
shaneos
4y ago
This makes me so, so happy! I put so much work into WebOS apps, and your site lists five of them. Sadly it's missing a few, like "My WebOS Apps", the developer dashboard app I wrote for WebOS app developers that let develope
77.
▲
by
shaneos
4y ago
Fun and deceptively difficult, nicely done!
78.
▲
Countdoku – Building a fast NextJS game with almost no JavaScript
(shaneosullivan.wordpress.com)
1 points
by
shaneos
5y ago
|
0 comments
79.
▲
by
shaneos
5y ago
Aphantasia: How it feels to be blind in your mind By Blake Ross https://m.facebook.com/nt/screen/?params=%7B%22note_id%22%3A... Before reading this post I had no idea I had aphantasia and thought everyone else was
80.
▲
by
shaneos
5y ago
For you fans of Phabricator macros, you can still get your meme hit on GitHub using https://gitme.me !
81.
▲
by
shaneos
6y ago
[author] It wasn't. The plan at the time was to deprecate Power Editor and build a new version of Ads Manager. We undertook both projects simultaneously, with the plan being to keep Power Editor going until AM v2 was ready. Unfortun
82.
▲
by
shaneos
6y ago
[author] This is very accurate. As the manager of the team I had to spend a huge amount of time trying to hire internally for it. No one came to FB to work on ads, they wanted to work on stuff that their friends used. I had to develop a
83.
▲
by
shaneos
6y ago
[author] Power Editor was originally written by a brilliant engineer named Vladimir Kolesnikov (yes, all by one engineer), and he was solving a very specific problem of letting customers scale their ad spend. So he chose a technology that
84.
▲
by
shaneos
6y ago
[author] Unfortunately yes. It was not the only thing happening at the time. FB had just gone IPO and this put a huge amount of pressure to grow revenue. When I joined the Ads org in 2012, it was about 100 people I think, with just a few
85.
▲
by
shaneos
6y ago
[author] Hard to say. If Google leadership had heard of this vulnerability, right as they were launching Google+, there would at least have been a serious conversation about it. They spent $Bs to build Google+, changed their whole company
86.
▲
by
shaneos
6y ago
[author] Many did and it was well earned. The team was awesome and had great camaraderie, but the work was horrible. Everything that broke led to a SEV for our team, even though 80% of the time it was not our code (somewhere deep in the A
87.
▲
by
shaneos
6y ago
[author] There were a number of critical parts of the chain responsible for FB Ads revenue. It all started at the UI or API (which were 75% and ~25% of FB revenue when I left in 2017). Then you had the DB layer, managed by another team, t
88.
▲
by
shaneos
6y ago
[author here] Getting 5 engineers was actually a huge ask. Just a year earlier the entire Ads Interfaces org had 5 engineers in it (I was #6). That was 5 engineers for all API and front end code for a $4B/year revenue company. Facebo
89.
▲
by
shaneos
6y ago
[author] There were some contingency plans, but we had no time to get them ready in advance. If Google had actually pulled the plug, we wouldn't been down for everyone for many weeks, and given that the vast majority of our large cust
90.
▲
by
shaneos
6y ago
[author here] Unfortunately no - we had many thousands of customers, most of whom had no control over their machines (low level employees at ad agencies). As a company, Facebook has no control over what browsers their customers use. The pr
More ›