edwintorok

Do you have a link to the 'Small Android Phone'?

That can be indeed very confusing when you initially learn the language. However there are 3 things that can help:

* An auto-formatter (ocamlformat integration in your editor, or ocaml-top) that shows how the actual nesting looks like

* You can add ;; at the end of a top-level function to get a syntax error at a better location

* Use the LSP integration of your editor which will show you where the error is as you type, so you catch the problem early

Lets try it on itself: > add bullshit: Paste crap, get truth.

Output: > Revolutionize your digital content strategy by leveraging our cutting-edge AI-powered semantic transformation platform to seamlessly transmute suboptimal textual inputs into crystal-clear, paradigm-shifting prose that resonates with your target demographic and drives engagement metrics through the roof!

Use above as input and get as output: > Use our AI writing tool to make your crappy text suck less and maybe get some clicks.

Slightly different one as input: > add bullshit: Bullshit Remover. Paste crap, get truth.

Output: > Introducing our revolutionary Linguistic Veracity Enhancement Solution™! This cutting-edge, AI-powered content optimization platform seamlessly transforms convoluted verbiage into streamlined, high-impact messaging. Simply input your suboptimal text, and our proprietary algorithms will distill it into pure, unadulterated truth nuggets. Elevate your communication paradigm today!

Reverse: > Bullshit translator: We made an app that cuts the crap out of your writing. It's not revolutionary, it's just a fancy spell-check. But hey, at least you'll sound less like a pompous ass when you use it.

Again: > We made an app that edits your writing. It's basically spell-check on steroids. It'll make you sound less pretentious.

Again: > We made a glorified spell-checker. It'll stop you sounding like a pompous ass.

Again: > We made a fancy autocorrect. It'll keep you from sounding like a pretentious jerk.

Again: > We made spellcheck. It'll stop you sounding like an idiot.

Again: > We fixed your typos. You're welcome.

Again: > We changed your words without asking. Deal with it.

...

TCP has a lot of offloads that may not all be available for UDP.

How do you find out what that keyboard shortcut is? I only found out when reading a similar article as the OP many years ago that complained about the removal of the textbox.

Otherwise I never would've known it is possible to activate the path textbox with a keyboard shortcut.

A UI needs to be both easy to use and discoverable. If "power users" have trouble discovering where the features they need are, why do we think the rest of the UI is easy to use/discoverable for everyone else?

(Although TBH I rarely use UI, and normally just use the terminal, except when upgrading the firmware of my keyboard, in which case I use Jade's file manager).

Is there a case where Google Docs or LibreOffice cannot open a docx or pptx correctly? I haven't used Word or Excel since their '97 version. Even at work I can't remember a situation where I specifically needed the MS implementation.

Interesting, I had the opposite experience: the GUI was very slow and nearly unusable on most RISC-V boards that I have, except the LicheePi4a. But that is probably just due to the GPU (which unfortunately doesn't have open source drivers yet?), and not the CPU, and they're all running different kernels and distros. When I have some time I'll need to compare again with the latest distro available for each, and also a fully open source one.

The description of interaction nets sounds a bit like hash-consing, with some extra optimisations.

If you overtrain the model may include verbatim copies of your training material, and may be able to produce verbatim copies of the original in its output.

If Microsoft truly believes that the trained output doesn't violate copyright then it should be forced to prove that by training it on all its internal source code, including Windows.