kimi

It's a fridge. Who knows what microcontroller CPU is there, and which toolchain they use.

You got my reference. But the original comment stands at -1 points now, even mock criticism of C and Rust seems to be totally unappreciated by the bigots.

Some crow experts discourage feeding them because they can be a bit too much.

OTOH the Swiss Department of Agriculture says that there is nothing that actually works against corvids. You can scare them and you can make their life difficult, but they learn, and show others how to bypass issues (possibly on "Corvid News"), so they might lose some battle but will win the war.

And nobody in their right mind sleeps soundly at night.

Or we realize that it is not possible, and Rust accepts to be "just" a definitely safer C.

Web apps work on input text and generate text, and C is not the most text-friendly language there is. There is a reason why early CGI-BINs were usually written in Perl.

(I won't even get started on the issues of creating new software in a language that is unsafe by design, and where any performance advantage will be dwarfed by the cost of forking. Whatever floats your boat, dude.)

I have some eye convergence issues, so maybe that's why. But my kids don't and they switched it off as well. Nice demo for the shop, though!

It was very nice, but very tiring after the first 5 minutes. So everybody I'm aware of switched it off in practice.

Every five years or so, VR gets to be the next hot thing. My first VR ride was on SGI Indigo, so it's been a while. Believers say we're almost there; I beg to be skeptical at this point.

The last part is incomplete but it reads like a report from an alien civilization.

I thought reddit would have been a sensible place to advertise our b2b product, that caters to a quite technical audience in a way that is not very friendly to Linkedin targeting.

We had a similar issue with Reddit, spent $500 and got a lot of clicks - none of them ever did anything else, not even by mistake. When we reported this behavior to Reddit, the rep who helped us set up the campaign just vanished. No answer. After a while, another rep came out and asked if we were interested in advertising on Reddit. Explained the situation and... poof! this other rep disappeared too.

My feeling is that this is systemic, and basically it's the very business model. I remember the first account explaining how the initial budget should be a few thousand dollars, so that "the AI could target effectively". It did target effectively - our wallet.

> Importantly, our results show that once a given system of communication has evolved, it may constrain the evolution of more efficient communication systems because it would require going through a stage where communication between signalers and receivers is perturbed.

You mean, they too used SMTP?

Remember the golden rule of Lisp macros: don't write a macro.

I'm sure it was posted previously, but it's always nice to read.

The first post seems to be from 16 years ago: https://news.ycombinator.com/item?id=1372371

I find it very useful to talk to my dog. When I have a problem I'm banging my head against, just explaining it to him from first principles makes my head "click". When that works, his dog treats are billed as "consulting".

The point is not launching companies, is making money with them.

Not sure i understand the point.... any p2p webrtc call in encrypted e2e.

This is now. But the seeds were sown much earlier.

The anti-nuclear area, at least in Western Europe, had historically a very high correlation with those who held sympathies for a certain very large nuclear power who would have strategically benefited from an anti-nuke sentiment that would avoid another nuclear power's weapon deployment in EU bases. But I'm sure it is a coincidence.

Archive returns 503 ATM....

Imagine when you receive millions of events per day -- the ones that arrive out of order, the days when delivery time goes up and up again, the days when oauth fails renewing keys... it's meant to be a lot of fun.

Compare to a sad websocket that just stays connected, you receive everything in order and you don't need an harness with tunnels every time you want to test something in dev.

Interesting to see the SDK making chat/bot integration simpler, but there's a whole other dimension to Teams integration that this doesn't touch: telephony.

The company I'm at has been been building call analytics for Teams since 2021 (QueueMetrics Live). A long-time customer migrated their entire phone system to Teams during the pandemic and asked my boss if we could follow them there. We said "in principle, yes": the Graph API exposes telephony events, so it seemed doable.

It was doable. It was also far harder than anybody expected. The Graph API gives you raw call records, but it doesn't model concepts like "wait time in queue" or "lost call" or "failed agent attempt", and whet it does, nowhere it written HOW. You have to reconstruct those from sequences of low-level events. We ended up building the whole processing pipeline in Elixir because we needed to handle the real-time stream reliably at scale. After a long beta and a few million calls processed, we got to GA. I was dabbling in Elixir at the time, I put it on my CV, and it was noted. In a sense, I owe Teams my current job (though I ended up on a different team, so I'm mostly referring coffee-mug lore here).

We set out to track queues and auto-attendants (that's our bread and butter from the Asterisk world), but we discovered we were seeing everything — inbound, outbound, Teams-to-Teams, even calls with other companies with their internal ids. You can get a complete picture of someone's telephony activity regardless of whether they work in a contact center or just use Teams as their phone. Most of the boring config (names, groups, codes) comes straight from Graph, which is nice.

Like it or not, a lot of enterprises are quietly moving their entire communications (including telephony) to Teams. When they do, they lose the monitoring and analytics they had with their old PBX. That's a real gap, and the Graph API — despite its limitations — gives you something to fill it. But I have a feeling that "3 lines of code" won't cut it. :-)

I was bitten by the same issue. Maybe add a line to the docs.

Actually, both will, as they are not separate within the LLM. The thing is, one is a style issue, the other content. You can express original ideas and still use a lot of em dashes, or produce slop with a lot of typos in it.

I have a pet-peeve with this. As a non-native English speaker, I find it very useful to dictate multiple notes, in different languages, and have the LLM produce clear English prose out of it. The prose may be LLM-generated, but I edit it when needed to make sure that the contents is 100% mine.

It's like dictating to a typist like they did in the 60's - he will make sure that your letter looks professional and will fix your grammar, but you will sign the letter. This is totally different from LLM spam, the kind that inflates a sentence into a three-page article full of nothing.

So - is it a problem if the language reverts to a mean? that is the point of a shared language, right?

Wish I had something like that when I was coding demos around 1988... :-)

(Edit): you kids have it easy.

Answering the question: it would be called "the Erlang VM", and you'd use Elixir to program it.

https://elixir-lang.readthedocs.io/en/latest/mix_otp/10.html

How is that relevant? we are talking about models, now what you do with them.

For text, have a big model generate the "intelligent" answer, and then ask a local LLM to rephrase.