Took a quick look at the Terms of Use and Privacy Policy. Notable gotcha: kids under 16 (in the EU, 13 elsewhere) are prohibited from using this.
(Also, it says "Au revoir mes petits choux!", and I think it's funny.)
Took a quick look at the Terms of Use and Privacy Policy. Notable gotcha: kids under 16 (in the EU, 13 elsewhere) are prohibited from using this.
(Also, it says "Au revoir mes petits choux!", and I think it's funny.)
Yet, for that specific web dev problem, I haven't seen any way of formally testing the rendering web pages, which would make it consistent on every browsers. The testing process (almost) always leave that up to the developers themselves, and refreshing pages is the norm.
We tend to call everything "software engineering" so that everybody can feel proud of such a title ("I'm an engineer"), but engineering is certainly not about figuring out how to vertically center divs with CSS (and it's also not about proving algebra theorems either -- even if it can be essential when it comes to specific problems that require it).
I can't imagine Linux and PostgreSQL being built without "science", they use a lot of it, and I'm pretty sure the authors all have read SICP and those theoretical books. Poking at things proved to be efficient to building things quickly, but it's just not how one builds critical systems/software that are robust, efficient and maintainable.
The following is an example of quite readable ELI with only a handful of symbols:
c,[1.5]32+1.8*c<-$_10+5**!10
It's not bad, but when all you have is ASCII, dense notation will inevitably look like line noise.APL's graphical notation was one of its original inventions, but custom keyboards weren't a viable solution in the PC era... But today the situation is different again. High-DPI displays and touch screens are becoming standard.
Would it be possible to reinvent APL notation to take advantage of high-res graphics and natural input methods? I'd love to see a tablet-only reinvention of APL that doesn't have a keyboard at all, just a number pad and painted gestures.
Most text editors operate text substitutions (like "<-" turning to "←" automatically), so ASCII doesn't seem inevitable anymore (and I believe it's even truthier with virtual keyboards).
I worked in a company where APL used to be very strong (large french truck manufacturer) and they even had lots of programs written in Scheme for assembly-line optimisations in the late 90s. Most of those have been rewritten (should I say... painfully rewritten, and now buggy) in Java in 2005.
I feel like APL/CLisps/etc. were the right solutions but developers/managers were/are scared when they saw some of the mathematical/proof concepts they had to use, and were afraid of when they learned about them at the university.
> CamelAI is an open-source, modular framework for building intelligent multi-agent systems for data generation, world simulation, and task automation. > [...] said Miguel Salinas, CTO, CamelAI.
1. CamelAI, where Miguel Salinas is CTO, their website is camelai.com, but it's not a an open source framework they offer. Their "AI data analyst" tool seems cool though.
2. CAMEL-AI, camel-ai.org, the actual open source multi-agent framework, and it also looks like some nice technology right there.