466 karma · joined December 24, 2010
It should be self-evident after a certain point (age) that approaching life through the lense of “what could give me an advantage over others”, whether that’s maths or just knowledge it won’t get you very far or if it does, it will at a severe cost on how you’re perceived in society furthermore interhuman connections will take a toll.
>One thing I want to note at this point is these findings are being misreported across the internet as evidence Fukushima’s radiation output is “spiking” or “soaring.” This is not the case.
>The radiation levels within Reactor #2’s containment vessel have been largely unknown for years, due to the difficulty of getting proper readings from remote equipment in the first place
In the context of life: it does derive itself from work i.e. I need work - other than that I don't believe in perfect balance, there's no such thing in life.
I'm usually trying to be an active nihilist i.e. less a passive one as much as I can. So I guess something in the realm of a “quest” of knowledge - the known unknowns and the yummy unknown unknowns.
- true parallelism (this is why we need guilds in Ruby 3)
- the BEAM
- functional yet OO at a higher level [0]
- all the Erlang/OTP goodies for free
- Phoenix/Ecto are quite nice frameworks and solid alternatives to the server-side JS world
- “looks” like Ruby though is an entirely different beast
Crystal on the other hand looks more like a Rust alternative to implement almost-as-C-fast Ruby gems. I'm sure it can evolve into an ecosystem but since it's quite far from being stable it will take some time, time in which the Elixir ecosystem will grow because its Erlang foundation already fixed the big issues.
[0] - https://www.infoq.com/interviews/johnson-armstrong-oop
The only issue so far is that the libraries ecosystem is indeed quite young but that is natural.
Still, Ruby (even without Rails) is at the moment a more productive environment.
I really hope Ruby "3x3" [0] will be released soon enough and projects like Hanami [1] become production ready so that it can coexist in a complementary way rather than becoming replaceable.
[0] - https://blog.heroku.com/ruby-3-by-3
[1] - http://hanamirb.org
Witches are connected to the BEAM? :) funny typo.
>Hanami components are decoupled each other. This level of separation allows you to use the ORM (data layer) of your choice. [0]
So indeed, one could use a preferred ORM. Yes the ORM looks a bit verbose and the part with the relations being experimental is a show stopper.
Ignoring all that, Hanami is quite nice architecturally speaking [1] it could evolve into the Phoenix of the Ruby ecosystem.
For example looking at the Phoenix framework - they choose by default Brunch [0] but they also let you implement whatever you want.
It's still opinionated but they make it clear is not part of the core framework.
I guess reading (not necessarily just philosophy) can have a cathartic effect and thus relieving some of the symptoms of depression.
And clearly, having a good therapist to talk to when nothing else works.
This may sound cliché but the "trick" is to try being aware of that threshold and when you pass it take some action or better yet stay away from it as much as you can using whatever works for you.
Isn't this a way to invite volatility into the Rails ecosystem? Maybe instead of adding options for webpack, yarn etc. Rails should decouple itself from the front-end so that most of us can use our Preferred approach™
Alternately something in the vein of moonglum's gem [0] should also work but again, as an external lib. not part of Rails.
[0] - https://github.com/fejo-dk/rails_external_asset_pipeline
The only problem is that like every social illusion it creates a social contract which makes it hard to get out of it - mostly because it will feel like being isolated from the "world" and in losing that perfectly crafted new "self/identity" will shatter the ego (we all know the ego doesn't enjoy being messed with).
Even if one is using it "just" for the messenger part, one is still part of all of this.
I'm not sure why would anyone use FB. to get new opportunities, FB. et al should not be taken seriously since most create their own persona on it akin to an MMORPG where one can literally choose to act like an Apache helicopter.
Moreover FB. is pure evil at its core: it's a global scale psychological experiment that future generations will refer to as: "those decades where everyone diluted their identity online, forgot about their "real" selves and thus slowly became clinically insane".
Some of the other arguments in the article are so broad that one can apply them to the Internet as a whole e.g. "distraction free work: just unplug your cable or disconnect your wi-fi"
Adding something akin to Guilds it could give it a nice advantage if implemented nicely.
>the Ruby ecosystem seems stale and lacking fresh ideas
I think that's mostly because it's not the new shiny toy what it's missing is some sort of cohesion to push it forward.
Maybe, I'm just biased but even with languages like Elixir - I keep coming back to Ruby.
[0] - http://kamome.lib.ynu.ac.jp/dspace/bitstream/10131/9368/1/id...
P.S. this is available via google results, I'm assuming it's public domain
Matz: 30% is huge.
Aaron: Yeah!
Jonan: That seems like a pretty good improvement to me.
Koichi: I do think so.
Aaron: We just need a few more 30% improvements then Ruby 3x3 is done.
Matz: Yeah, that means 30% of the time is spent in the compiler.
EDIT: maybe they were joking once again?
For me the slow start-up and the JIT requiring ~50K/req for warm-up just ruin the whole experience in coding the app in Ruby I'd rather just use Elixir.
Another interesting project is IBM's OMR [0] - compared to JRuby there are no slow start-ups and weirdly, being still a dev. preview it can run Rails and its deps. without issues, even better than Rubinius stable.
Just by playing around with RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR you can reduce memory consumption quite a bit.
I don't really have a problem with the tone of the interview but more with how vague the proposed objectives are.
Also, there seem to be some rather misleading facts in it - like the AOT and the 30% speed-up - in practice, after testing it - it helped to load Rails faster but other than that the benchmarks were virtually identical (don't get me wrong, booting Rails faster is great but they imply something completely different in the interview)
980M - 100W / 1060 ~ 80W / 1070 ~ 120W / 1080 ~ 150W
If they started out with the max TDP of 100W for the cooling system - upgrading it to 150W in that small space it sounds like too much of a change to meet their DL?
Clearly this does not excuse the reengineering but it might explain why they went this route.
Again PHP (the language) vs. Rails (the framework).
What framework was that `big php app` using?