Re: dlangbot for Telegram - D compiler in your pocket
On Sunday, 10 June 2018 at 19:54:20 UTC, Dechcaudron wrote: On Saturday, 9 June 2018 at 20:28:24 UTC, Anton Fediushin wrote: Hello, I am glad to announce that new Telegram bot which can execute D code is up and running! Check it out here: https://t.me/dlangbot Features: - Two compilers to choose from: dmd (default) and ldc - Support for custom compiler arguments with `/args` command - It's possible to set program's stdin with `/stdin` - Code is automatically compiled and ran again when you edit your message Repository: https://gitlab.com/ohboi/dlangbot Any ideas on how to improve it are appreciated! As much as I love Telegram bots and D, compilation and execution offered by a bot provides no clear advantage to me (still, I kinda like it). I assume you are looking out for potential vulnerabilities? How about allowing for download of the executable? This bot has the same purpose as run.dlang.io - a sandbox to try some things and share code with people. Even though sharing can be done with simple 'highlight your message with code and bot's reply -> share these messages' I am thinking about ways to make it simpler and faster. Regarding vulnerabilities, if there are any I and authors/maintainers of dlang-tour will be interested in fixing them ASAP. After all, dlangbot uses tour's code under the hood. Executable downloading would require me to rewrite the back-end. I am not sure if it'll worth it because it's not clear how safe that would be for a user and how usable that feature will be. I mean, if user already has x86-64 Linux machine (that's what dlangbot uses) then will it be any simpler and faster to message the bot with code, download an executable and run it than compiling it using installed compiler?
iopipe v0.1.0 - now with Windows support!
iopipe version 0.1.0 has been released. iopipe is a high-performance pipe processing system that makes it easy to string together pipelines to process data with as little buffer copying as possible. Nothing has really been changed, but it now has Windows i/o support. I will note at this time, however, that ring buffers are not yet supported on Windows. This version deprecates the IODev type that I had included, in favor of a new io library that shows extreme promise. This version ONLY builds on 2.080.1 or later (the bug fix that I submitted at dconf has been merged in that version, and so iopipe will now build against Martin Nowak's io library). In fact, iopipe development was kind of stalled due to this bug, so I'm super-happy to see it fixed and released! Note that the new io library also supports sockets, which IODev did not have support for, AND has a pluggable driver system, so you could potentially use fiber-based async io without rebuilding. It just makes a lot of sense for D to have a standard low-level io library that everything can use without having to kludge together multiple types of io libraries. Near future plans: 1. Utilize a CI to make sure it continues to work on all platforms. 2. Add RingBuffer support on Windows 3. Add more driver support for std.io. 4. Continue development of JSON library that depends on iopipe (not yet on code.dlang.org). git - https://github.com/schveiguy/iopipe dub - https://code.dlang.org/packages/iopipe docs - http://schveiguy.github.io/iopipe/ -Steve
Re: dlangbot for Telegram - D compiler in your pocket
On Saturday, 9 June 2018 at 20:28:24 UTC, Anton Fediushin wrote: Hello, I am glad to announce that new Telegram bot which can execute D code is up and running! Check it out here: https://t.me/dlangbot Features: - Two compilers to choose from: dmd (default) and ldc - Support for custom compiler arguments with `/args` command - It's possible to set program's stdin with `/stdin` - Code is automatically compiled and ran again when you edit your message Repository: https://gitlab.com/ohboi/dlangbot Any ideas on how to improve it are appreciated! As much as I love Telegram bots and D, compilation and execution offered by a bot provides no clear advantage to me (still, I kinda like it). I assume you are looking out for potential vulnerabilities? How about allowing for download of the executable?
Re: GitHub could be acquired by Microsoft
On Sunday, 10 June 2018 at 00:29:04 UTC, bauss wrote: And then Microsoft acquires both and everyone moves to Bitbucket. Endless cycle :) Until people figure out decentralization. AIU scuttlebutt server provides only discovery service, these proved to be able to run at little cost. And as tox shows, even discovery can be decentralized too.
Re: GitHub could be acquired by Microsoft
On Monday, 4 June 2018 at 20:00:45 UTC, Maksim Fomin wrote: On Monday, 4 June 2018 at 19:26:23 UTC, Joakim wrote: On Monday, 4 June 2018 at 19:06:52 UTC, Maksim Fomin wrote: Unlikely, you don't spend $7.5 billion on a company because you want to send a message that you're a good dev tools company, then neglect it. You have no idea about how big corporations' management spends money. As with Nokia and Skype - I don't know whether it was initially a plan to destroy products or management was just silly. I suggest you look at their online slides linked from the Nadella blog post to see their stated plan, such as integrating github into VS Code more: http://aka.ms/ms06042018 and likely vastly overpaid for an unprofitable company in the first place :) this is exactly how such deals are done - paying $7.5 bl. for nonprofitable company. Unfortunately, their books are unavailable because they are private company, but scarce information in the web suggests that in most of their years they have losses. Just as rough estimate: to support $7.5 bl valuation Microsoft must turn -$30 ml. net loss company into business generating around $750 ml. for many years. There is no way to get these money from the market. Alternatively, the project can have payoff if something is broken and Microsoft cash flows increase by $750 ml. This is more likely... but they emphasize that they intend to keep github open and independent. They can claim anything which suits best their interests right now. Or, as alternative, github can be broken in a such way, that their promises on surface are kept. Business is badly compatible with opensource by design. I just finished reading this interesting article by a former Microsoft business guy, which makes the same point I did, that MS is unlikely to neglect github or otherwise force it in some direction to leverage it: https://stratechery.com/2018/the-cost-of-developers/ You're right that MS has had many acquisitions go badly already, such as Nokia and Skype (though I'd argue both were long-term doomed before they were bought), but, as always, incompetence is the much more likely reason than malice.
