Nick Olinger

47 posts

Nick Olinger banner
Nick Olinger

Nick Olinger

@olingern

Staff Software Engineer @GoFundMe | NYC

Brooklyn, NY เข้าร่วม Mart 2024
73 กำลังติดตาม22 ผู้ติดตาม
dax
dax@thdxr·
please shut the fuck up i don't even care about the specific thing you're saying i'm just so tired of hearing predictions one after the other telling me what the future is going to be like just please shut the fuck up
English
400
892
14.8K
619.3K
Nick Olinger
Nick Olinger@olingern·
@mitchellh I love using ghostty and wouId love to contribute one day. I hope there's a way where low quality PRs could be reduced or auto-closed, but PRs from first-timers who spent the time to learn, test, and work through changes could land
English
0
0
0
92
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
I've been doing open source since I was a teenager (over 20yrs). And for the first time ever, I'm considering closing external PRs to my OSS projects completely. This will throw the baby out with the bathwater and I hate that, but we close auto-opened slop PRs every single day.
English
153
113
2.7K
205.8K
Nick Olinger
Nick Olinger@olingern·
@kepano My iOS obsidian hasn’t been functional for a while. It’s probably an iCloud issue, but I wish there was more information on what’s stalled so I could debug
English
0
0
0
86
kepano
kepano@kepano·
Performance is design, and every millisecond counts. Every update in 2025 trimmed Obsidian's load speed. This is quite complex given the number of different configurations and operating systems Obsidian supports. We employed many different solutions to speed up Obsidian across various syncing methods, operating systems, plugins, vault sizes, etc. Getting into Obsidian should be instantaneous regardless of vault size. It's absolutely necessary so that ideas can flow without friction. Obsidian has always been performance-focused, but one problem area was startup time on mobile. That has radically improved over the last few updates, and it's now down under 500ms for almost all vaults, even my large personal vault with over 17,000 notes. As of Obsidian 1.10 the app becomes usable after initialization and core plugins, the rest loads in the background. In 1.11 we're shaving off a few seconds with widgets so you can open/create directly from the lock screen. You also have the ability to choose how the app opens by default (e.g. new note, existing note). You can even bind Obsidian to your action button. There's still more time we can shave off. Believe me, as someone with a large personal vault, I notice every bit of slowness everywhere it happens, and I won't rest until we shaved it all away.
kepano@kepano

opening files in Obsidian, not sped up — ez

English
68
114
3.9K
531.5K
Nick Olinger
Nick Olinger@olingern·
@mattpocockuk @_devJNS I wouldn’t ignore it. You can spend a lot of time debugging “this” changing scope. Arrow functions are safer for beginners but I personally don’t like how they’re formatted — functions look more consistent across large codebases
English
0
0
0
336
Matt Pocock
Matt Pocock@mattpocockuk·
@_devJNS Ignore this, just keep shipping
English
8
9
743
26.4K
JNS
JNS@_devJNS·
regular functions or arrow functions?
JNS tweet media
English
153
71
1.5K
69.3K
Nick Olinger
Nick Olinger@olingern·
@aarondfrancis The idea that a declarative string can have some implication on how my application runs is wild. I prefer working within the language and not magical semantics
English
0
0
6
331
Nick Olinger
Nick Olinger@olingern·
Thoughts on making Github PR review better. Lots of cool ideas coming from people answer @jaredpalmer 's question
Nick Olinger@olingern

@jaredpalmer @github Large PR management has been challenging. Echoing similar thoughts as @devongovett Other comments: 1. AI code review is really valuable, but no way to get rid of the posts. I want to "clean up" a PR and its comments

English
0
0
0
55
Jared Palmer
Jared Palmer@jaredpalmer·
How can we make @GitHub Pull Request and code review experience better?
English
835
56
1.5K
513.7K
Nick Olinger
Nick Olinger@olingern·
@pilcrowonpaper @16kbps I think 120 is the magical line length. Beyond, on smaller screens you have to scroll but is ample enough to not break lines at the thought of a TypeScript type
English
0
0
0
24
pilcrow
pilcrow@pilcrowonpaper·
@16kbps no global print width, only wrap code when it makes sense like multiple (+long) function arguments, array items, object properties, etc
English
1
0
4
285
pilcrow
pilcrow@pilcrowonpaper·
Really wished there was a js formatter that was much more conservative with code wrapping
English
3
0
28
3.7K
ThePrimeagen
ThePrimeagen@ThePrimeagen·
the video is still up
ThePrimeagen tweet media
English
445
125
4.6K
842.8K
Nick Olinger รีทวีตแล้ว
Steven ⬢
Steven ⬢@styfle·
Did you know that Node.js 22 has glob built in? No dependencies needed. #fspromisesglobpattern-options" target="_blank" rel="nofollow noopener">nodejs.org/api/fs.html#fs
Steven ⬢ tweet media
English
12
50
676
45K
Nick Olinger
Nick Olinger@olingern·
I will say — npx sst remove went without a hitch, so that was cool
English
0
0
0
17
Nick Olinger
Nick Olinger@olingern·
The coolest thing about sst, without question, is the `link` feature where you can inject a resource, like a queue into your application and not even think about policies. When it worked, it felt amazing.
English
1
0
0
21