If the goal is decarbonation, using wind+solar is alright (renewables are a bigger part of the mix in Germany) but burning gas and lignite when there's no sun or wind is not.
In Germany the problem is coal (lignite): it remains a huge social and political 'asset'. Many jobs, low-priced electricity, no dependency towards fuel shipped by a foreign nation...
After Fukushima most German citizens didn't want nuclear reactors anymore:
Which political parties switched most of the nuclear plants off since Fukushima?
CDU/CSU: 14
FDP: 11
SPD: 9
Greens: 3
(source: https://x.com/HannoKlausmeier/status/1784158942823690561 )
I'm also a French taxpayer, I regret coming back to France every time I read about something stupid they do with our money. This Pneumatit thing is really something.
It was because of the bad things I read about warranty/support that I bought my Note Air 3 on Amazon. I paid a bit more but at least I knew I could return it easily if there was an issue.
I got pretty good results with the autoimmune protocol (pain-free plus no more brain fog after 3 months of the elimination phase.) I talked about it to my GP who told me to do an allergy skin test, because blood tests were not 100% reliable.
In the pre-LSP era, I worked as a novice Scala developer, and I didn most of my Scala work in Emacs with ENSIME. It was pretty good. I imagine the language server is pretty usable by now.
Hi o/ Hopefully the goal of CIEL is well explained. I use it daily (with the core image, in my editor), I ship products with it. It saves me a load of time, when I start a new project, when I need to interact with the outside world, when I want to write a little something and ship it on the server without Python's mess, etc. Speaking of which, Django is of course difficult to replace, but I started an automatic DB dashboard for CRUD operations, something's on the way (unreleased).
I integrated CL step by step for my clients' work, and CIEL is another means to this end. To use CL, for real. None of my projects need CL's superpowers, but I want them for development, deployment and monitoring!
---
Today I fixed a few issues and released a v0.2: https://github.com/ciel-lang/CIEL/releases/tag/v02 The key point is that CIEL should be much easier to install, specially on Mac. We now rely on many less system dependencies.
If you find out that CIEL is still difficult to install on your platform, don't hesitate to send details on an issue. Thanks in advance.
---
TLDR; May CIEL ease and soften your CL journey.
ps: you have no idea how much time it took me to discover certain things! Now you have them here, ready, packaged :-]
Yes I do, of course, and I actually use it nearly exclusively for multi-file projects: I don't write short scripts everyday, but I have bigger projects that need more features. The one I am on: extract data from an existing DB, format it, save it to a csv, send it with SFTP. I build a binary and send it to my servers.
For this I use :ciel as a dependency, I use a typical project structure: a system definition in an .asd file (that :depends-on (:ciel)), and sources. I also start my editor with CIEL's core image. I build a binary the usual way out of this, I don't run this app as a script, specially if I added a couple dependencies. But that's OK, I benefited from CIEL during development.
I recommend to start with a file packages.lisp that defines 1 (one) package for the whole application, to use it across multiple files, until it makes sense to create a second package. Otherwise, one can easily loose oneself into export & import symbols hell, specially when we are new at it. So I don't recommend the "one-package-per-file" approach.
Hopefully the Cookbook gets you covered if you need examples.
France: 40g/kWh Germany 557g/kWh
If the goal is decarbonation, using wind+solar is alright (renewables are a bigger part of the mix in Germany) but burning gas and lignite when there's no sun or wind is not.
reply