* 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

Comments URL: https://news.ycombinator.com/item?id=42177411

Points: 37

# Comments: 12

Comments URL: https://news.ycombinator.com/item?id=42116669

Points: 2

# Comments: 0

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.

...

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).

* use framepointers [1]

* use LBR (but LBR has a limited depth, and may not work on on all CPUs, I'm assuming due to bugs in perf)

* implement some deep changes in how perf works to handle the 2 stacks in OCaml (I don't even know if this would be possible), or write/adapt some eBPF code to do it

OCaml 5 has a separate stack for OCaml code and C code, and although GDB can link them based on DWARF info, perf DWARF call-graphs cannot (https://github.com/ocaml/ocaml/issues/12563#issuecomment-193...)

If you need more evidence to keep it enabled in future releases, you can use OCaml 5 as an example (unfortunately there aren't many OCaml applications, so that may not carry too much weight on its own).

[1]: I haven't actually realised that Fedora39 has already enabled FP by default, nice! (I still do most of my day-to-day profiling on an ~CentOS 7 system with 'perf record --call-graph dwarf -F 47 -a', I was aware that there was a discussion to enable FP by default, but haven't noticed it has actually been done already)

https://www.xenserver.com/story

We build and ship a Linux distro that runs on Xen as its control domain (Dom0). This role is about developing and maintaining the public API server: https://xapi-project.github.io/. There is both a junior and a senior role.

The majority of the control-plane is written in OCaml, with some Python scripts, and OCaml<->C bindings. The codebase is more than a decade old, and has >240K lines of OCaml code, most of which is open source. We have an automated test suite that exercises various OS and x86-64 CPU families every night.

Vacation: 25 days/year + UK bank holidays. Salary depends on the position, with opportunities for advancement, and bonuses depending on individual and business unit performance. Private pension plan, and health insurance.

Apply directly for one of these positions https://careers.cloud.com/jobs/senior-software-engineer-xens... https://careers.cloud.com/jobs/software-engineer-xenserver-t...

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.

But even if it did an exact match search is not enough here. What if you take the source code and rename all variables and functions? The filter wouldn't trigger, but it'd still be copyright infringement (whether a human or a machine does that).

For such a filter to be effective it'd at least have to build a canonical representation of the program's AST and then check for similarities with existing programs. Doing that at scale would be challenging.

Wouldn't it be better to: * Either not include copyrighted content in the training material in the first place * Explicitly tag the training material with license and origin infornation, such that the final output can produce a proof of what training material was relevant for producing that output and don't mix differently licensed content.

Disclaimer: I work here

Disclaimer: I work here

See VM.pool_migrate and VM.migrate_send https://xapi-project.github.io/xen-api/classes/vm.html. Those features got introduced in Xenserver 4.0 (2007) and 6.1 (2012).

Disclaimer: I work at XenServer.