News for hackers. Stuff that matters.
Re:The Rust Platform by goodplay on Wednesday July 27, 2016 @10:52PM (#12178042)
If you can, could you elaborate more on python's stdlib holding it back? I think batteries-included experience is one of the reasons why so many people (including myself) use python.

It's also one of the features I sorely miss when using Rust. Luckily, Rust's stdlib is starting to tend towards being more practical with recent additions like system time.

Re:The Rust Platform by sitkack on Wednesday July 27, 2016 @11:15PM (#12178109)
The 'std lib is where libraries go to die' was invented by Python. The libs are shallow, don't break backwards compat and provide a substandard experience. Things that continue to improve provide an out of tree alternative package name. Python codebases that are resilient don't use much of "core", arrow for time, requests for http, simplejson, etc. Using core is an antipattern that will get you stuck on a version of the language which is ridiculous.

Linking the language and the libraries together is a mistake.

Re:The Rust Platform by pjmlp on Thursday July 28, 2016 @03:32AM (#12178870)
I disagree.

In the enterprise space it is quite common that we only get to use what it is in the computer and access to anything else is strictly controlled by IT.

So if it isn't in the standard library or some internal library mirror, we don't get to use it, as simple as that.

Re:The Rust Platform by hsivonen on Thursday July 28, 2016 @04:34AM (#12179063)
I think it would be terrible for Rust design/evolution/policy be constrained with that kind of enterprise badness that basically bans crates.io, and crates.io is an awesomeaspect of the Rust ecosystem.
Re:The Rust Platform by pjmlp on Thursday July 28, 2016 @05:25AM (#12179239)
I can tell it is lots of "fun" when you can only use a Maven mirror, with approved jars.

To get a jar into that mirror, a request needs to be sent to the legal team describing the license and business case use, after approval the IT team will add the said jar to the mirror.

The same applies to version upgrades of already approved jars.

This is a typical scenario I had already in a couple of projects.

Re:The Rust Platform by adrianN on Thursday July 28, 2016 @06:16AM (#12179393)
I agree that this sucks, but not doing it that way is dangerous for the company because developers might not care enough about license compliance when they include some stuff into their project.
Re:The Rust Platform by pjmlp on Thursday July 28, 2016 @06:50AM (#12179487)
I also agree, as I have been through what happens when developers do exactly that and then it gets discovered the worse way.
Re:The Rust Platform by wilmoore on Saturday July 30, 2016 @03:44AM (#12192048)
You willingly subject yourself to this? Why?
Re:The Rust Platform by hibbelig on Saturday July 30, 2016 @09:30AM (#12192887)
Just a guess: it pays the rent.
Re:The Rust Platform by Manishearth on Thursday July 28, 2016 @06:07AM (#12179364)
It's not a constraint as much as it is a consideration imo.
Re:The Rust Platform by lmm on Thursday July 28, 2016 @04:54AM (#12179130)
So maybe there's value in shipping a "standard bundle" that includes popular libraries or some such. But it's not worth distorting the whole language design to accommodate bad policies.
Re:The Rust Platform by pjmlp on Thursday July 28, 2016 @05:26AM (#12179244)
Might be, however those bad policies are quite standard in big corporations.
Re:The Rust Platform by wilmoore on Saturday July 30, 2016 @03:43AM (#12192044)
I see where you're coming from, but I feel like it would be a mistake to expect the language or std lib to try to solve problems that are effectively organizational/cultural issues.
Re:The Rust Platform by glandium on Thursday July 28, 2016 @01:10AM (#12178425)
Plus, python's std lib is a mumbo jumbo of all sorts, there is no API coherence.
Re:The Rust Platform by oblio on Thursday July 28, 2016 @03:45AM (#12178913)
That's a failure at the moment of inclusion. I'm guessing it was done for convenience and to increase adoption (getting decent libraries in the standard library faster).
Re:The Rust Platform by _ZeD_ on Thursday July 28, 2016 @02:28AM (#12178688)
Just as a data point... I like and heavily use the core libs... And not once i used arrow, request or simplejson, while knowing them, because i didn't feel the needs
Re:The Rust Platform by the_mitsuhiko on Thursday July 28, 2016 @03:29AM (#12178861)
Then you most likely have various security or logic problems in your application unfortunately.
Re:The Rust Platform by fnord123 on Thursday July 28, 2016 @08:20AM (#12179724)
Arrow seems particularly useless as it just wraps stdlib datetime and its awful 10 byte size rather than moving to an 8 byte representation like np.datetime64 uses.
Re:The Rust Platform by rspeer on Thursday July 28, 2016 @12:31PM (#12181282)
Just because you haven't found a use for it doesn't mean it's useless.

The stdlib datetime class is terrible and desperately needs to be wrapped. Arrow is a good wrapper. I don't know what you're on about with counting bytes.

Re:The Rust Platform by fnord123 on Thursday July 28, 2016 @05:32PM (#12183342)
I've wrapped datetime for company work (pre pandas, pre datetime64) to make sure it follows the rules of the data analysis platform we developed (adding functions for moving to next month of year based on various financial calendar rules for example). I wish I hadn't done it and had just wrapped a boost_datetime since the performance of datetime is slow when you have a large timeseries of them. The performance is especially unacceptable if you also have timezones attached to your datetimes.

Now we have pandas, yay. But I don't see why one would use arrow. If you're patient enough, could you explain why you would use it? The website doesn't seem to be very convincing.

Re:The Rust Platform by rspeer on Friday July 29, 2016 @03:43PM (#12189413)
Not everything is a DataFrame. You would use Arrow because you want a nice API for dates and times in use cases that have nothing to do with Pandas.
Re:The Rust Platform by rtpg on Thursday July 28, 2016 @06:52AM (#12179490)
But isn't requests built off of urllib?

The thing I like about python is it gives tools for library writers to build things without going too low level.

Application writers will always write with better libs, but don't have to worry about third party lib compatiblity on platforms because of the stdlib serving as a virtual machine (most of the time)

Re:The Rust Platform by BAKfr on Thursday July 28, 2016 @07:30AM (#12179579)
requests is built on urllib3, and it includes its own version of urllib3 (to avoid dependency problems).

If I'm not mistaken, the stdlib contains urllib and urlib2, but not urllib3.

The fact that there 3 "urllib" packages show that the Python way is not so good.

Re:The Rust Platform by lmm on Thursday July 28, 2016 @04:56AM (#12179139)
Many libraries in the stdlib have much better alternatives, because libraries with their own release cycle can evolve much quicker. But people get stuck on the "standard" version because it's what's in the stdlib. Worse, people write for compatibility with whatever was in stdlib 2.4 because that's what RHEL6 ships.