HN user
my workaround for this was to make a wrapper mcp server which uses claude haiku to summarize the page snapshot returned in the response of each playwright mcp call, and that has worked pretty well for me: https://github.com/jsdf/playwright-slim-mcp
he doesn’t want experts, he wants people who will be subservient to him. expertise would get in the way of that, because experts would likely understand that he has no idea what he’s talking about, and not respect his dictates. see: everyone who knew how things worked at twitter.
'authenticity' in the sense of content made by normal people without any strong goals other than 'some other people might like that' (and for some, maybe eventually getting some income from monetization) rather than highly produced content with the goal of reaching the largest possible audience and extracting the largest possible amount of money from that, which is what reels feels like. if you want to see that type of 'more authentic' content, tiktok's approach to populating your feed will be much more responsive to that than instagram's. there also seem to be a lot more people creating content on tiktok aimed at that level.
just to be that guy
Module.onEnemyKilled();Module.onEnemyKilled();Module.onEnemyKilled()
modular synthesis isn't named 'modular' in reference to 'modulation', it's in reference to synth 'modules', which are units of functionality from which you can build a synthesizer. for example with an oscillator module, a couple of envelope modules, a gain module and a filter module you can build a typical monophonic subtractive synthesizer.
the ‘search box’ is not good at finding stations so i can check when the next train is coming. i typed in ‘34th st’ and it returned a bunch of addresses, none of which are in manhattan. this is probably because you require me to type ‘34 st’ exactly (no ‘th’) instead. if you can’t fuzzy match this, this search box is just unusable.
i also tried looking at ‘nearby stations’ and while standing on the 34th st A platform it didn’t list the 34th st subway station at all, just a bunch of bus stops.
please let me just look at a station list instead.
well as long as we're posting them: https://github.com/jsdf/applescript-raytracer
if you prefer the macintosh version: https://jamesfriend.com.au/pce-js/mecc/oregon-trail.html
I did the browser port of BasiliskII which this wraps (https://jamesfriend.com.au/projects/basiliskii) as well as the port of PCE (another Macintosh emulator) used on archive.org.
I see a lot of people asking why someone would distribute an Electron-wrapped version of a program you could run natively, and I see it as an extension of the the same reason why I ported these emulators to the browser in the first place: accessibility. While you can install BasiliskII natively, it's a bit of a pain, especially if you are not super technical. If you find a binary floating around online it may not work for your OS version. Wrapping it in Electron is one way to ameliorate the OS compatibility issue; Chromium has been battle-tested across many OS versions. Ideally BasiliskII would have a better OS compatibility story (as well as being more portably distributable with data files) but, like many open source projects, it doesn't have a lot of maintainer-time to make this happen.
You can experience this on an (emulated) 68k Mac in your browser using Oldweb.Today: https://oldweb.today/?browser=ns3-mac#http://68k.news/
If you're using SSR (or static generation) for the initial pageload, you can continue to do so. The payloads can just be used to update the page when the user performs subsequent interactions.
Additionally, you can always fall back to clickable links if you really want to support subsequent interactions for users with no JS, if you've built the routing infrastructure for that
can you describe the threat vector here? how exactly could it be used to do that? keeping in mind the cross origin limitations mentioned in the spec, and that the timing resolution is no different to JS timestamp methods already available to code run in this context
If you want to try out the HyperCard application for yourself (for example, to see its editing tools) you can do so in the browser here:
https://jamesfriend.com.au/projects/tryhypercard/
For Mac users, you can also easily run it on your local machine: https://jamesfriend.com.au/running-hypercard-stack-2014
Also, if you're taken by the HyperCard aesthetic, you be interested in this interactive artwork created in HyperCard (which I contributed technical assistance to): https://www.upprojects.com/projects/commissions/formality/
if electron is not to your taste, you can run the emulator in your browser here: https://jamesfriend.com.au/projects/basiliskii/
coincidently today firefox 79 was released, which brings back support for SharedArrayBuffer, which is a key part of the browser port of this emulator
The author mentions that they didn't have a debugger and couldn't get MacsBug to work inside the emulator. A useful technique here is to use the emulator itself as the debugger: most emulators have features for setting breakpoints and single stepping through emulation and directly reading memory values from the emulated system's memory (by absolute memory address). For example, here is the documentation for 'hardware'-level debugging in the PCE emulator: https://github.com/jsdf/pce/blob/pcejs/doc/monitor.txt
One 'nice' thing about working with old architectures like classic Macintosh is that there is basically no abstraction between the software and the hardware, so manipulating the behavior of the emulated hardware becomes a powerful debugging tool.
You might be interested in this GDC talk about the PS4 Spiderman game, which dives into the performance optimizations they used, which are in a similar spirit (though at a higher level of abstraction): https://www.youtube.com/watch?v=KDhKyIZd3O8
Your link seems to be broken, here's a working version: http://web.archive.org/web/20040313034855/http://www.gamasut...
Interestingly the N64's RSP has some instructions specifically intended for implementing MPEG decoding (ctrl+f for "MPEG"in http://ultra64.ca/files/documentation/silicon-graphics/SGI_N...)
You're right, Scottish English does seem like a foreign language sometimes...
it's almost like different companies make different tradeoffs based on different organisational needs and priorities
San Francisco needs more public restrooms. I think any map of SF's poop should also show how few city-provided restrooms there are, so I made one: https://sf-restrooms-and-poop.glitch.me/
Compare with Australia's National Public Toilet Map: https://toiletmap.gov.au/Find/20547
This article is about the instagram.com website, not the mobile app. Are you talking about the website or the mobile app?
It's actually the PCE emulator, not vMac: https://github.com/jsdf/pce
I was surprised to see all the people on this site (who should know better) trying to evaluate someone based on lines of code.
Also, it seems like this article is falling surprisingly fast down the front page. dang can you confirm whether this is getting aggressively flagged?
This appears to be using my port of the PCE emulator[1]. It's also used on the Internet Archive, which has a collection of HyperCard stacks which you can run in the browser[2].
I have a short tutorial[3] for running HyperCard stacks locally which might be interesting to anyone who has some stacks lying around on their filesystem, or who just wants to play around with Mac OS 9.
[1] https://jamesfriend.com.au/pce-js/
How did you extract concerns from class components and reuse them previously? Easy and hygienic extraction and composability of concerns literally is something new enabled by Hooks that was not offered by class components.
You're also misrepresenting what the docs say about replacing class components. They're saying that you don't need to replace class components just for the sake of using 'the new thing'. However if there was some concern you wanted to extract from a class component that you could not previously, you absolutely could adapt it to use hooks, and then extract and reuse that concern in another component.
How is this different to using a React component installed from npm? You can look inside them if you want to, but don't have to. That is the goal of abstraction.
If you want to have no abstraction and show all state in your component, just don't extract any into Custom Hooks. Then it's really not very different to a class component.
Here is a visual example of how hooks move all the parts of a single concern into a single block of code which, in a class component, would be littered across lifecycle methods: https://twitter.com/threepointone/status/1056594421079261185
Grouping these parts this way means they can be trivially extracted as a Custom Hook[1] (analogous to a 'mixin' or 'trait' in OOP).
By extracting this concern into a Custom Hook it can easily be reused by different components, as well as composed by other Custom Hooks. This was previously possible using Higher Order Components, Render Props and the (really old) React Mixins concept, but Hooks addresses problems with each of these previous approaches.
If you want to know more about how Hooks improves over these previous approaches, see my previous comment: https://news.ycombinator.com/item?id=19074469
If you're interested in playing with an Atari ST but don't want to install anything, there's an in-browser emulator on my website here: https://jamesfriend.com.au/pce-js/atari-st/