Cohost

But wouldn't the same apply to condition variables, not just semaphores? Also I found another reference to that internal post here https://cohost.org/Catfish-Man/post/913314-a-love-letter-to-os

> It would be different if the software made you promise (by contract, for example) to not go below a certain price. From the reporting of this over the past 2 years, it became very clear they required them to accept the prices. > Specifically, every morning, RealPage provides participating Lessors with recommended price levels. ... If Lessors wish to diverge from the “approved pricing” they must submit reasoning for doing so and await approval. ... But RealPage emphasizes the need for discipline among participating Lessors and urges them that for its coordinated algorithmic pricing to be the most successful in increasing rents, participating Lessors must adopt RealPage’s pricing at least 80% of the time. https://cohost.org/morayati/post/925436-i-saw-real-page-s-cra

One interesting read on the topic of near misses and High-Reliability Organizations is the paper "Going Solid", which has a great summary here: https://cohost.org/mononcqc/post/888958-paper-going-solid

The key difference is this: > [E]very morning, RealPage provides participating Lessors with recommended price levels. Lessors typically must communicate to a RealPage “Pricing Advisor” that they have “accept[ed]” or “confirm[ed] the “approved pricing” within a specified time frame. If Lessors wish to diverge from the “approved pricing” they must submit reasoning for doing so and await approval. [...] > But RealPage emphasizes the need for discipline among participating Lessors and urges them that for its coordinated algorithmic pricing to be the most successful in increasing rents, participating Lessors must adopt RealPage’s pricing at least 80% of the time. This organization was enforcing 'discipline' among the participants to make sure that they didn't undercut each other too often. That's a cartel. 1. https://cohost.org/morayati/post/925436-i-saw-real-page-s-cra

I love this horrible, clever, horrible tech and this writing style. The first paragraph links to a related earlier post, and I can confirm it’s also worth reading in case you skipped it: https://cohost.org/cathoderaydude/post/1228730-taking-the-deepest-p

A similar technique for building bridges is known as "falsework"[0], where you build a "bad"/simple/basic framework, that is used for supporting the final, ideal bridge or other mechanical work. [0]: https://en.wikipedia.org/wiki/Falsework Fred Hebert has an excellent post on cohost[1] about this. [1]: https://cohost.org/mononcqc/post/467669-a-bridge-over-a-rive

These are called sub-types or pattern types, and they are not in the language. But they are something I would love to have. You can’t emulate them with GAT unfortunately. https://cohost.org/oli-obk/post/165584-ranged-integers-via

>The old WebGPU meeting notes have some choice quotes from (IIRC) Unity and Adobe engineers literally begging the committee not to invent a new shader language. This was an interesting tidbit, so I tried to find the source for it. While I did not find it, I did find the December 2019 minutes[0] which has a related point: >Apple is not comfortable working under Khronos IP framework, because of dispute between Apple Legal & Khronos which is private. Can’t talk about the substance of this dispute. Can’t make any statement for Apple to agree to Khronos IP framework. So we’re discussing, what if we don’t fork? We can’t say whether we’re (Apple) happy with that. I found this link via rust hn[1] which I found after reading this blog post:[2] >Vulkan used a bytecode, called SPIR-V, so you could target it from any shader language you wanted. WebGPU was going to use SPIR-V, but then Apple said no The lobsters thread also links to a relevant HN post:[3] >I know, I was there. I also think that objection to SPIR-V wasn't completely unfounded. SPIR-V is a nice binary representation of shaders, but it has problems in the context of WebGPU adoption: It's so low level [...] It has a lot of instructions [...] Friction in the features we need, vs features Khronos needs. [...] there is no single well specified and tested textual shading language. HLSL doesn't have a spec. The linked blog post from lobsters was also discussed on HN, which you also commented in.[4] It would be great if…

https://cohost.org/ ?

Unfortunately, most alternatives to Mastodon seem to be either explicitly right-wing (which you may or may not care about) or designed to copy and consume Twitter's business model, and aren't likely to be any better than Twitter in the long run. Mastodon really is the best alternative at the moment, and it doesn't have to be difficult (although the most difficult option - self hosting your own identity server - is also the most secure.) You can find hosting solutions or even do what I (the laziest person) did and just run multiple accounts through each instance's public website and use browser bookmarks and/or a third party client. Not much more difficult than joining subreddits, but more annoying in that there is no actual shared identity between accounts. Plenty of political activists and media services are already on the platform. But since you asked, I found some, with what seemed to be the biggest or most recent HN discussiona I could find. Absolutely no guarantees on my part regarding utility, practicality, security or whatever, though. Nostr protocol: https://github.com/nostr-protocol/nostr https://news.ycombinator.com/item?id=33746360 Bluesky: https://bsky.app/ https://news.ycombinator.com/item?id=33323815 Counter Social: https://counter.social/index.html https://gizmodo.com/jester-hacker-trying-to-fix-social-media-counterso… (^weirdly no HN traction on this one tha I could find) Cohost:…

I am adding a blog post, shared on HN a couple months ago, that show an architectural cross section of the city. https://cohost.org/belarius/post/6677850-architectural-cross (I am not the author of the blog, nor the original poster, but I just want to share the link because I found this incredibly cool)

Also relevant, as you alluded to, cohost is now read-only and will be shutting down at the end of 2024. https://cohost.org/staff/post/7611443-cohost-to-shut-down

A bit gauche that “the full panorama” link hotlinks the CDN of a dead social media site (cohost) without citation. Far more information about the print can be found in the corresponding post there: https://cohost.org/belarius/post/6677850-architectural-cross.

Skip Mastodon, BlueSky, or Threads, join cohost by the anti software software club, a software company that hates the software industry: https://cohost.org/rc/welcome // On second thought, cohost sign-ups are closed, as it's shutting down end of year. Turns out Twitter alternatives are hard to keep going, even if all you're doing is changing your name from Twitter to X.

The more relevant post is the the one from the cohost maintainers linked in that post’s first comment: https://cohost.org/staff/post/6403911-may-2024-financial-u. In summary, at that time Stripe forbade use of their service to pay for tips or subscriptions that do not result in access to exclusive content.

I assume they're referring to this: https://cohost.org/corru/post/6551052-ko-fi-and-stripe

I read a post some time ago that explained how that test came to be - It was created by Ryan Gosling of all people - and it's an incredible story inside an incredible story. Not sure if this [1] is the post I read back in the day, so I hope it does explain the story correctly (Haven't read this one in particular, just googled for it). Then I thought "May be I picked that from Hacker news" [2] and [3] (May be you should go at these in reverse order) [1] https://cohost.org/mcc/post/178201-the-baseline-scene [2] https://news.ycombinator.com/item?id=35813595 [3] https://www.denofgeek.com/movies/blade-runner-2049-how-a-key-scene-dif…

The Ars writeup is blogspam, the linked original post has much more detail: https://cohost.org/ghoulnoise/post/5286766-do-not-buy-hisense-t

Rust is considering this under the name of "pattern types" [0][1]. If the full idea is realized, you should be able to handle strings and enums as well. There is also a PR for a minimal implementation using a macro and targeting integers specifically[2]. It's experimental and there is a chance this doesn't get stabilized, but here's hoping it makes it through! [0]: https://github.com/rust-lang/rust/pull/107606 [1]: https://cohost.org/oli-obk/post/165584-ranged-integers-via [2]: https://github.com/rust-lang/rust/pull/120131

Checkout the "css crimes" tag on cohost, there's some pretty cool stuff there! https://cohost.org/rc/tagged/css%20crimes

From a comment on the blog post: > iirc it's generated from a script in asterisk, with the delay and tone durations set "short" (I think it was the minimum EIA/TIA DTMF mark/space numbers, not sure.) > My phone system was Google Voice, through an SIP bridge with Obihai (now defunct/discontinued). Asterisk then made the SIP connection and rang my other phones, a Lucent Partner ACS for my landlines, cellphones, ATAs and forwarding numbers, also over SIP. > Most of the hardware was lost in the housefire last year. This recording was from early-mid 2020 or so. https://cohost.org/sirocyl/post/2891449-i-broke-ikea#comment-4f432d10-…

This might be it: https://cohost.org/whitequark/post/3963011-the-yowasp-toolchain https://marketplace.visualstudio.com/items?itemName=yowasp.toolchain https://yowasp.org/ https://vscode.dev/github/YoWASP/toolchain-demo

Not really. Many wanted Vulkan for the web. But Apple virtually had a veto, apparently: https://cohost.org/mcc/post/1406157-i-want-to-talk-about-webgpu

With the old Macintosh Programmer's Workshop (MPW; a text-based shell for Mac OS of the 80s and 90s) there was similar functionality called Commando for almost every command. The commando information was kept in a 'cmdo' resource. Something similar could be done today with extended attributes, if support wasn't so hit or miss. Oh, apparently, A/UX had commando as well. If you double-clicked a terminal command from the Finder, it would pop up the commando box to choose your CLI options, then run it in a shell window. Today, running a terminal command from Finder just runs it without any arguments in a shell window. https://cohost.org/boredzo/post/804893-i-still-want-a-moder http://toastytech.com/guis/aux3.html

Url changed from https://cohost.org/mononcqc/post/3647311-paper-you-want-my-p, which points to this.

What do you mean? nevi-me's comment linked to this: https://cohost.org/ThePhD/post/2720152-mn#comment-fdd4ee8d-9c12-47b0-8… That's, like, the core thing in my disagreement with nevi-me. It would've helped if you read nevi-me's comment before you decided to join the discussion. I don't understand why you believe you're in a position to say what anyone "should" use as criteria for picking a language. If a language's leadership and most prominent community members were mistreating me and lying about me for half a year I might want to avoid that language too.

This reminds me of the ‘dropping in’ technique used by actors. https://cohost.org/mcc/post/178201-the-baseline-scene

Edit: I misread your question, so responded with a link to this article answering "why WebGPU": https://cohost.org/mcc/post/1406157-i-want-to-talk-about-webgpu It does seem like kind of a mess. Unlike WebGPU, though, it doesn't sound like Meta's thing is much of an improvement.

This post goes into a lot of detail: https://cohost.org/mcc/post/1406157-i-want-to-talk-about-webgpu

Currently writing my own software rasterizer, some interesting stuff I came across: Fine grained visibility determination (span, coverage buffers, etc) https://www.flipcode.com/harmless/issue01.htm Tom Forsyth, How To Draw Ugly Lines Fast https://cohost.org/tomforsyth/post/648716-how-to-draw-ugly-lin Ned Greene, Hierarchical Polygon Tiling with Coverage Masks https://www.cs.princeton.edu/courses/archive/spring01/cs598b/papers/gr… This UC Davis lecture video explains rasterization rules really well: https://youtu.be/z3fWd7G3mrU