3 ms·
> BossDB migrations aren't particularly advanced. No, they aren't, they were "the simplest thing that possibly worked" for my needs (I wrote that code). One
by davidw 12y ago
> BossDB migrations aren't particularly advanced.
No, they aren't, they were "the simplest thing that possibly worked" for my needs (I wrote that code).
One problem with boss_db is that it uses some heavy duty compiler magic that none of the "pure Erlang" kinds of folks really want to touch because it produces un-Erlangy code. This leaves it in a no-man's land: the Erlang people don't want to deal with it, and the people coming in from Ruby or whatever are just going to go straight to Elixir which looks more familiar anyway.
- vezzy-fnord 12y agoThe implication here being that the Ruby folks mostly care about surface convenience, with not even using parser transforms to provide parameterized modules (remember, one of the reasons people laud Elixir so much is its metaprogramming support) to overload the language a bit and provide ActiveRecord-like patterns being enough. It's not really an indictment on Erlang, though. The situation you present is unwinnable.
- rambocoder 12y agoIMHO when Ericsson decided to remove "experimental pmods" support from Erlang in version 16, the compiler magic in ChicagoBoss turned from "oh cool" into a liability. Ericsson's development team did release a workaround example, but the whole process how this went down left a sour taste in my mouth. My wish is that Ericsson's Erlang development team became more transparent to the outside world, shared their bug tracker, code reviews (Go team does this wonderfully) and did all development in the open. Then we would not have these situations https://github.com/erlang/otp/pull/687 https://github.com/erlang/otp/pull/687 and it would save me ton of time couple years ago chasing after ssl bugs.
- davidw 12y ago> when Ericsson decided to remove "experimental pmods" support from Erlang in version 16, the compiler magic in ChicagoBoss turned from "oh cool" into a liability. It caused a bit of hassle, but not much, really. It was a feature that many Erlang people did not like much in the first place, so heavy use of it put them off to begin with.
- rambocoder 12y agoI agree with you that it wasn't that much of a hassle technically, just wish that the announcement was done with more transparency instead of "OTP Technical Board" met somewhere and this is what was decided http://erlang.org/pipermail/erlang-questions/2012-October/069720.html http://erlang.org/pipermail/erlang-questions/2012-October/06... Reminds me of Microsoft's .NET development process from 10 years ago, huge corporation drives development of a platform behind closed doors with very few people from the outside having any idea what is coming in the future.
- rambocoder 12y agoI wonder if IEUG made any more progress on their TODO list https://erlangcentral.org/industrial-erlang-user-group/join/ https://erlangcentral.org/industrial-erlang-user-group/join/ in Publishing OTP backlogs and Public issue tracker...
- kungfooguru 12y agoThe Ericsson team does plan to open up things like that. But pmods shouldn't be used like an example of them going against the community in driving the language forward. Very very few people in the community objected to their removal. Many of us were happy and thought it should have happened much earlier.
- davidw 12y ago> The Ericsson team does plan to open up things like that. It seems they have been planning it for a while. One of the things that looks nice about Elixir is that there is a lot of doing, as well as planning.
- kungfooguru 12y agoRemoving features is a lot harder than adding them :)