Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Even with the other form, if pip imports anything named like a pyhon module in the dl dir, it will be imported. That's because the current dir is automatically added to the PATH, using -m only add pip.py to the attack surface.


You should always use this form if outside a virtualenv.


What's the differences between python and ruby import systems ?


That they never had a problem with one.

I’ve never had a problem with python’s import system either.


Is this a case of "netflix did those articles, so we'll do the same so geeks like us too"?


It does seem like a fad. Kudos to those who can create a new field and profit from it. On the one hand, "chaos engineering" seem a bit like "we don't understand our architecture well enough to know what its failure modes are, so let's just poke it and see what happens," but on the other hand, it seems at least a little bit analogous to fuzzing, which is certainly a technique that yields useful results that would have otherwise been overlooked until it was too late.


My first instinct was to agree with this, but from my experience it's extremely difficult to properly communicate failure modes 100% of the time across different teams in very large organizations. Dependencies that are fuzzy arise for example when a service A proxies data for client service B from some other service C. It doesn't help that the organization of teams in a company often severs lines of communication between teams who explicitly don't have dependencies but implicitly do. As a result, information gets lost in the process. Having a last line of defense in the form of a "chaos engineering" team may actually be the natural response of large organizations to counter the inherent messiness that is produced as a result of bureaucracy.


That and additionally it has implications for the development team as well. Using "chaos engineering" shifts the mindset of the developers. As a developer you now expect things to fail. You know that the "we make it work first and make it resilient later" approach will bite you sooner then later so you think resilience from the first line of code.


You don't know what all your failure modes are. You probably think you do, but you don't. That's the point of chaos testing.


There are a million different ways a computer can fail. I think we're asking too much of people to be able to know all the pitfalls of every system they create.

But also this 'new field' just seems like something we've already been doing just with a different name. You're kind of expected to make sure your system can work if the computer suddenly shuts off, or a dependency is lost, or the network is slow. Have we not been doing this??


It does seem antithetical to engineering, though. Are there other engineering fields that take this approach?


> On the one hand, "chaos engineering" seem a bit like "we don't understand our architecture well enough to know what its failure modes are, [...]

That approach seems like a good idea, even if you think you know what the failure modes are.


If nothing else, the article showcases how to use the recently released AWSSSMChaosRunner[0], which I hadn't heard about. Beyond that, it's good when multiple different high quality blog posts show how to do what's fundamentally the same thing.

[0] https://github.com/amzn/awsssmchaosrunner


Definitely seems like a case of someone that wanted to publish a blog post for some internal kudos, but I'm not complaining. Always good to share knowledge.


It sounds like complaining to me


My guess? Someones manager was like "Hey lets publish this wiki as a blog post."

Sure, part of it is trying to seem cool and whatnot, but that's fine with me. The output is the same, more knowledge shared.


Never thought I’d see anti-article sentiment on HN, and more generally, not sure what sort of response you expect to generate. Why comment at all?

To avoid more of the same, I’ll say that the article itself is pretty detailed, but whereas Netflix blog-posts are more general, this one feels hyper-specific. That’s great if you’re tied to aws, but I think the former has longer-lasting + further-reaching utility.

Hope they do more.


Not an anti-article sentiment, but I dislike the trend of big companies pretending they care about the nerds just because they realize they need them for one particular objective.

It's an anti-marketing sentiment.


That makes more sense. I think it’s worth framing differently, though.

Big companies aren’t writing the doc, per se. Engineers interested in the material are. And often, they want the opportunity to do so - it’s something of a stamp for “expertise” in their favor.

Assuming the post is actual quality, it’s a marketing win for the company, a professional/developmental win for the employee, and an informational win for everyone else.


> Aren’t you just repeating some stereotypes you heard elsewhere? If France were as hostile as you pictured it, how would it have such a dense startup ecosystem and even (God forbids!) some very successful ones?

Where are they? Cause as a French, I've been living on the startup scene for 10 years, and I don't see those anywhere. There are successful companies, but startup?

I hear about a 1000 more US ones than french ones, while I'm literally living next to an incubator.


Is it fair to compare France to USA though ? In term of scale maybe comparing to Europe would be better.

Are you both saying that you are "living on the startup scene" but don't see any startup ? Or any successful ones. On the top of my head I can already cite you Blablacar, CapitaineTrain, Dailymotion, Deezer as relatively successful for the French market ... Of course if you're looking for planetary mastodon as sign of success ...


Those are not successfull start ups, those are companies that make money.

There are plenty in france.

The startup model assumes you use VC cash to drive explosive growth.

Bla bla car took 13 years to slowly becomes the average company it is, being covoiturage.fr before. Deezer barely makes a dent in spotify market despite the fact it was born before. Even french don't know about daily motion, it survives because of all the pirated content it contains. Captain train had a moment, and lost it. The oui sncf service has won. At least if you disagree, none of them scream "explosive growth" in my mind.

I'm not saying there are no successful startups. Meetic and free are examples of that in there times.

But there's not a lot of it. Next door, ledger was midly successful, and maybe kryll will do something if they manage to get binance on board and then add the forex to their targets, but I don't see a uber, stripe, dropbox, etc. anywhere.


Do you have any ball bark value you could estimate for the size of a bare bone common array implementation?

I'm dreaming of having basic numpy features in the Python stlib, but numpy is so huge, and I have no idea how much of it is the array itself, and how much are all the tooling around it.


If arrays are standardized, we may even see a future where they end up being in the stdlib, while libs like numpy, dask, etc. will mostly provide tooling to work with them.

This would be a huge deal, allowing pure Python libs to suddenly exist for a whole lot of things like image/video manipulation, advanced stats, and so on, without requiring compiled extensions.

I love numpy, but having to install the 100Mo beast is overkill for a lot of use cases. Not to mention restricted environments where you can't.

Well, one can dream, no?

Imagine having a numpy-like array as a primitive. Suddenly you can make the case for a K/J-like DSL embedded in it like regexes are for text. Suddenly Python-fast enough perfs are getting an order of magnitude higher. Suddenly you get a powerful shared buffer for multiprocessing.


A good first step in that direction would be writing a solid PEP. But I'd say that it would be helpful to have a common standard ready first.


J should be a dsl for array embedded in other languages, the way regexes are for text.


In a sense, it is simple: simple to understand.

Not simple to solve.

Like to win a race Usain Bolt, it's simple, run faster!

Fortunately, Python is well equipped for that. If you open a file with Python that you know it might contains mixed encoded text, you can use try/except to inform the user or open in binary mode, and just store the binary.

But my favorite way of doing it is:

    open('file', error=strategy)
Strategy can be:

- "ignore": undecodable text is skipped

- "replace": undecodable text is replace with "?"

- "surrogateescape" (you need to use utf8): undecodable text is decoded to a special representation which makes no human sense, but can en rencoded back to it's original value.

It's kinda ironic because people bashed Python for separating bytes/text, forcing them to deal with encoding correctly in Python 3. After all, this problem of "slamming bytes together" comes from languages that treat text as a bytes array, allowing this stupid mistake.


Yeah, that was more or less my approach to analysis for these files. Essentially it was an export that was quasi-aware of Unicode and dumped out certain fields (of course they had to be variable length) in their original encodings, whatever they were. I got more than a few of these.

Unicode is great, as long as everyone upstream follows all of the rules and nothing goes wrong.


How do they take into account the insects that were in areas turned into fields, industries and cities ?

Are there traps there as well ?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: