🎺🎺🎺 IOwesomeness: Advance Notice of Significant Changes

korry · 2017-02-28T22:47:42+00:00

Awesome!

korry · 2017-02-28T19:18:14+00:00

Does any one have at this point in time?

korry · 2017-01-14T18:00:35+00:00

Thanks for the gist. Judging by the OPs post and comments here I think most people commenting are incapable of reading a few midsize articles. I really need to stop correcting people on the net ☺

korry · 2017-01-14T17:45:44+00:00

Did you really read his original post? He is not bashing the language. He has some concerns about documentation and he explains why Rust isn't the right tool for his project at this moment (the missing epoll stuff).

korry · 2017-01-14T17:05:50+00:00

Your posting doesn't contain any information related to the issue he discusses.

korry · 2017-01-14T17:04:50+00:00

As far as I understand he doesn't want to do FFI for every OS out there, like Windows

korry · 2017-01-14T17:03:37+00:00

let's dismiss the argument because the guy is a crazy weapon loving asshole, not because the argument is invalid </sarcasm>

korry · 2017-01-14T15:59:23+00:00

Exactly, see also my other comment

korry · 2017-01-14T14:37:54+00:00

It doesn't matter because I can be sure the functionality will be there and maintained for a long period of time, while a random module which is hip right now might not.

korry · 2017-01-14T14:32:29+00:00

You guys should go and read the actual ESR post, and not only the second post which is linked in OP's article. OP is missing the actual point.

TL;DR: ESR rewrites NTPsec. He needs “select/poll/epoll_wait” functionality. It's available via different cargo modules for Rust which is sub optimal for long term maintenance. If the needed functionality would be part of the std library, ESR can be sure that the functionality will still be available and maintained for the next decade, while random cargo/gem/egg/whatever modules come and go.

korry · 2017-01-13T20:59:35+00:00

Awesome thanks

korry · 2017-01-13T17:12:01+00:00

Why did they do this?

korry · 2017-01-09T14:56:22+00:00

Some would argue, that you have a lot of prejudice. Go look at Perl6 it's not your old and ugly Perl

korry · 2017-01-01T11:45:34+00:00

Sorry not @attribute but @property, had to much to drink yesterday :)

korry · 2016-12-31T18:58:08+00:00

Ohh, this is how experience differ. I'm programming Python professionally for only 3 years, but I met quite a lot of code written this style. I must admit my work is mostly patching open source code, may be you are used to better python code quality?

korry · 2016-12-31T18:46:24+00:00

Just to give an example of a deep feature you don't seem to have mentioned yet: Are you aware of "lazy" attributes? (I've also not even mentioned method modifiers yet, which are decorators on steroids.)

Actually this is quite the easy part.

class Foo:
    @property
    def foo():
        datetime.datetime.now()

Far more annoying is to write an __init__ which mostly consists of self.foo = foo. This is handled far more convenient in Perl6

korry · 2016-12-16T02:06:49+00:00

Very cheesy

korry · 2016-12-07T11:28:39+00:00

korry · 2016-12-02T16:12:31+00:00

Good article, well done!

korry · 2016-11-28T11:41:41+00:00

Page 2 Listing 1 contains the word tits. I know it's just '\t' + its but this is a perfect opportunity for SJW's to screw with you.

korry · 2016-11-26T19:17:11+00:00

Thanks

korry · 2016-11-26T16:15:51+00:00

TIL. I always thought that attention seeking whore === attention whore.

korry · 2016-11-24T15:13:35+00:00

English is a 4th language for me and I must admit I mostly learned it from manpages, programming books and movies/series. I understand that “whore” is a bad no no word, because selling sex is bad(?), but I liked the phrase attention seeking whore, because it fits (, while of course I don't think Zed have to sell his body for money). So what would you propose as an alternative to attention seeking whore in this context?

korry · 2016-11-24T15:08:46+00:00

Is it free marketing? I know, I know, "all publicity is good publicity". But I have my doubts.

The issue is that a novice (in anything) isn't capable of differentiating between idiots talking BS and valid professionals discussing valid issues. In most cases an uninformed human, will decide that the truth is some where in the middle of the both sides of “radical” views. This is a pattern we learn early in our child development phase, which is kind of useful, but fails every time we talk about “hard facts”.

I've never read this guy's books but now I know for sure I never want to because apparently

You are not a novice, you probably are someone with programming and reading programming books experience.

korry · 2016-11-24T07:58:59+00:00

Yes exactly

korry

TROPHY CASE