oblosys

4 ms·

1.
by oblosys 9mo ago
Happy to help!
2.
by oblosys 9mo ago
I almost got tricked into trying to figure out what was Easter eggy about August 9 2015 :-) There's a clarifying tooltip on the link, but it is mostly obscured by the image's "Archive" title attribute.
3.
by oblosys 11mo ago
I was kind of expecting to hear Toto in the background. https://maxsiedentopf.com/toto-forever/
4.
by oblosys 1y ago
When I asked GPT-4.1 to show some references to confirm an answer was as widely accepted as it claimed, it replied with a bunch of unrelated GitHub issues with fake descriptions, and this Stack Overflow link: https://stackoverflo
5.
by oblosys 4y ago
With these declarations your fragment is valid in both JavaScript and TypeScript: class b {} class c {} const d = JSON.parse const a = Promise.prototype.then.bind(Promise.resolve(1)) console.log(a<b,c>(d)) &
6.
Show HN: React-hook-tracer – A light-weight tracer for React hooks(github.com)
2 points by oblosys 4y ago|0 comments
7.
by oblosys 4y ago
It removes the shadow around the window.
8.
by oblosys 4y ago
Just noticed that with this method, the backspace joins the two lines, whereas in the original it reveals the markup, but the newline between the lines remains.
9.
by oblosys 4y ago
Just to clarify, this is not how I created the original document in 2004 :-) There were certainly no paragraph styles involved, and the edit actions had to include an undo, or it wouldn't happen. There was also no style inspector yet.
10.
by oblosys 4y ago
Cool! This was pre-XML Word, and since introducing it became impossible at some point, I always just figured it had been a bug. Probably the bug was only in the creation, as I do remember the sequence of edit actions made no sense. I think
11.
by oblosys 4y ago
Unfortunately, I lost the recipe (18 years is a long time), but I vaguely recall that the first line had markup that got canceled out, and that trying to delete the newline somehow deleted the end tag for that markup instead of the newline.
12.
by oblosys 4y ago
I ran into it while editing an interview text that had colors for people's names. It was surprisingly easy to reproduce, but creating the buggy documents got fixed at some point. The font and styles were altered slightly for dramatic e
13.
by oblosys 4y ago
Here's a bug I discovered in MS Word in 2004, which has survived the past 18 years of updates and is even present in the web version: https://1drv.ms/w/s!AgYiBqBjIZZpfkcvO9jnOel9T2o?e=tFA4wp If you join the two li
14.
by oblosys 5y ago
Hmm, this could actually be useful: [][(![]+[])[+[]]+(![]+[])[!+[]+!+[]]+(![]+[])[+!+[]]+(!![]+[])[+[]]][([][(![]+[])[+[]]+(![]+[])[!+[]+!+[]]+(![]+[])[+!+[]]+(!![]+[])[+[]]]+[])[!+[]+!+[]+!+[]]+(!![]+[][(![]+[])[+[]]+(![]+[])[!+[]+!+[]]+(!
15.
by oblosys 7y ago
For a do-it-yourself version of chapter 1 (about building complex circuits using only nands), I can recommend http://nandgame.com/
16.
by oblosys 7y ago
The monolith/microservices discussion always reminds me of this 'Sandboxing Cycle' xkcd: https://xkcd.com/2044/
17.
by oblosys 7y ago
For me that didn't work. The red badge on System Preferences disappeared, but it came back the next day. Doing a `defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier` got rid of it permanently.
18.
by oblosys 8y ago
Youtube video showing some of the persistent life forms: https://www.youtube.com/watch?v=iE46jKYcI4Y
19.
by oblosys 8y ago
Looks like this is the location on Google Maps: https://www.google.nl/maps/@53.6885648,-6.4832216,763m/data=...
20.
by oblosys 8y ago
Inspired by StackOverflow questions on React's new lifecycle methods, I created a light-weight package that visualizes which lifecycle methods are called and in what order. It can be installed with `npm -i react-lifecycle-visualizer`,
21.
React-lifecycle-visualizer v2.0 released(github.com)
1 points by oblosys 8y ago|1 comments
22.
React v16.4.0: Pointer Events(reactjs.org)
3 points by oblosys 8y ago|0 comments
23.
Show HN: Real-time visualizer for React lifecycle methods(github.com)
4 points by oblosys 8y ago|0 comments
24.
by oblosys 9y ago
Before switching to React, I learned a lot about Angular from https://teropa.info/build-your-own-angular/
25.
by oblosys 9y ago
Npm has alpha versions react@16.4.0-alpha.0911da3 and react-dom@16.4.0-alpha.0911da3 you can experiment with.
26.
by oblosys 9y ago
One option is to make the input component uncontrolled by removing the value={this.state.password} prop, but keeping the onChange handler to maintain the password in the state for validation & strength checking. Typically, the only time
27.
by oblosys 9y ago
If you use React, updating the value on every change is a very common pattern.
28.
by oblosys 9y ago
The inheritance example is incomplete, as it should do `Editor.prototype.constructor = Editor;` after `Editor.prototype = ..`. Without this, `david.constructor` will be `User`, and a check like `david.constructor === Editor` will yield fals
29.
by oblosys 9y ago
Well, obviously it's easier here, but just because something is easier doesn't automatically mean resources will be allocated to do it well. I was pleasantly surprised that at least for some newer projects Microsoft seems to do a
30.
by oblosys 9y ago
There are also Microsoft teams that don't put you through such nightmare scenarios though. Last night I submitted a TypeScript bug report, and within 15 minutes it was labeled, added to the next-release milestone, and had someone assig

More ›