I moved onto a domain of my own. My personal blog now is at http://monodes.com/predaelli/
I would like to edit my posts on the front-end of my blog, using https://wordpress.org/plugins/wp-front-end-editor/
I would also like many of the masonry themes from wordpress.org.
Sadly there are only two masonry themes and no front-end editing here in WordPress.com. So I would move this little blog on a self-hosted, sub-blog in a domain of mine quite soon.
Our online solution offers free e-mail address hosting for a wide public in search of a high quality service inspired by a free philosophy and totally independent of all the existing large service companies on the web. The respect for our members’ privacy is our priority, which is why we do everything to ensure the security of the data that is entrusted to us.
Yet, even if they tell us who they are, even if I now value my privacy and freedom, I still wonder how they will pay data and power bills, not to mention hardware costs and people work.
I do know that Google’s price is privacy and advertizing. I do know that WordPress.com insert advertizing.
Ok, I feel stupid. I’m reading several weeks of unread mail discovering this one of 26th of march:
Hi Folks, I’m happy to announce CastXML, a successor to GCC-XML . CastXML is hosted here: https://github.com/CastXML/CastXML#readme
It is a tool based on LLVM/Clang that generates the same XML output format as GCC-XML . CastXML’s design offers some advantages over GCC-XML’s:
- LLVM/Clang offers a true SDK for external tools, so CastXML does not need to maintain a fork. GCC-XML requires significant work to update its parser to a more recent GCC. CastXML can simply be built against a recent LLVM/Clang.
- LLVM/Clang natively supports parsing both GCC and Visual Studio system headers, so CastXML does not need to maintain a set of system header patches. GCC-XML must be updated with system header patches for each new version of compilers it supports. CastXML can simply parse the headers directly.
- CastXML will need little to no work to support newer GCC and Visual Studio versions as they are released. LLVM/Clang maintainers already take care of this. Due to the above, CastXML supports recent versions of Visual Studio, while GCC-XML does not support VS 2010 or later.
- CastXML can parse in some language modes besides C++98, though since the output format currently matches GCC-XML, only C++98-compatible interface structures appear in the output. For discussion of CastXML please join the mailing list for that project rather than posting on this gccxml list. The CastXML mailing list is here: http://public.kitware.com/mailman/listinfo/castxml
- Thanks, -Brad
 If anyone is interested in continuing to maintain gccxml please contact me off-list to volunteer.
 The output format is intended to be close to gccxml’s format to make porting clients easy. There may be some differences where output constructs depend on internal compiler implementation details.
While I have promptly cloned their git repository I’m not sure I want to start using CastXML as I discovered the gcc-plugin packages which should allow to directly plug in into gcc.
It may look somehow moreconvoluted. Indeed it may be actually more convoluted. In fact Gcc “stubbornly” refuses to be subdued into a library. It will call your code. According to the “Parsing C++ with GCC plugins” serie that I pointed out previously it don’t look so frightening anymore, at least to me.
Since my aim is to work on the GNU Eiffel compiler it is wise to use Gnu Compiler Collection
I can’t believe it is that simple
Fix linux DNS issues with .local addresses on MS domain
Microsoft uses .local as the recommended root of internal domains, and serves them via unicast dns. Linux uses .local as the root of multicast dns. If you’re stuck on a broken MS network like this, reconfigure your linux multicast DNS to use a different domain like .alocal.
To do this, add a “domain-name=.alocal” line to the “[server]” section of “/etc/avahi/avahi-daemon.conf”, then restart avahi-daemon: “sudo service avahi-daemon restart”.
Tutti sappiamo bene quanto i dispositivi Android siano legati a Google ed ai suoi servizi; sappiamo anche che le applicazioni di Google non sono Libere o Open Source; sappiamo bene, infine, che tutti nostri dati passano per i server Google, sotto gli occhi di chiunque abbia accesso ad essi (qualcuno ha detto NSA?).
Per nostra fortuna la community di sviluppatori ed appassionati, nata intorno all’universo Android, è vastissima e questo ha portato, grazie alla grande porzione di codice dell’OS distribuita con licenza libera dall’AOSP (Android Open Source Project), alla nascita di moltissime alternative libere (CyanogenMod, tanto per citare la più famosa) e non solo.
La maggior parte di queste ROM non presenta le applicazioni Google preinstallate, per motivi di licenza. Questo fa sì che, una volta installate, il dispositivo sia virtualmente (dico “virtualmente” perché non è possibile avere la certezza assoluta che sia così) libero dal…
View original post 955 altre parole