1,326 karma · joined October 26, 2012
That said, if the seller makes a mistake then they need to rectify it entirely, they can't demand you wait around for a courier at an inconvenient time or get you to pay for postage.
If others want this feature, it's tracked in https://github.com/Microsoft/vscode/issues/5953
Denying people a right that's commonly understood to be fundamental to international law and then using violence to enforce it is repression in my book. Spain has consistently escalated tensions rather than offering a path to a real democratic decision. They're going to have to accept the repercussions of that decision.
I think the real problem is that Spain have consistently blocked a peaceful referendum. I don't believe Catalonia would vote to leave in a fair vote, but I do feel that the repressive actions of the Kingdom of Spain on this matter are the kind of thing that could justify declaring independence unilaterally.
12 factors into 2, 2 and 3. If a column is index 2n or 3n it will never contain a prime after the first row. The columns that match that here are: 2, 3, 4, 6, 8, 10, 12. The columns that don't are 1, 5, 7, 11 - your four.
Copyright of literary characters is one of the harder ones to define, and perhaps a system more like patents would be more appropriate for them, but that's neither here nor there.
Let's stick to computer science for a while. Imagine I have come up with a sorting algorithm for integers with significantly better time complexity than existing options. I can describe that in any number of programming languages, in natural language, in pictographs, etc. It's a skill that people can learn, or a tool that could be embedded in silicon and used for financial gain. Doesn't that sound more like an invention than a creative work? Shouldn't patents be the best fit?
Don't get me wrong, copyright and patent systems the world over hace significant class, but for us as software engineers to declare that patents shouldn't apply to our work because it is somehow fundamentally different to the other science and engineering disciplines is just arrogance.
The kind the patent trolls use are not innovative in the same way. We need a stricter definition of obvious to one versed in the art, not a ban throughout the field.
The short form of the problem is where you say "No offset can be used more than once." where you actually want "No offset can be used unless it is higher than all previously used offsets".
Consider an assassin and their controller using this scheme for designating targets. Garry is first, the controller sends
10, 13, 16, 19, 22 = garry
The security services intercept this and notice that garry is killed.They now know that 0-9 != g, 11-12 != a, 14-15 != r, 17-18 != r, 19-21 != y
They suspect that either andi or rory is the next target, the controller orders Andy killed and sends:
0, 15, 17, 27 = andi
The security services can then infer that the person to be killed is matched by the regex: ^[^g][^r][^r].$
andi matches, rory doesn't.It's much better to treat your random characters as numbers to add to the your data mod 256 (in your ASCII 256 example), and also set rules like fixed message length and scheduled messages that can be 'no-op'.
I suspect there are a few confounding factors. Firstly, lots of non-residents travel to tech conferences in the US. This gives them a wider pool of people to reject. My personal experience is that US-Americans are underrepresented at conferences in other places. They're by no means absent, but it feels off to me.
I do think that even controlling for that it happens more in the US than other countries, though. Of my colleagues who travel a lot I don't know anyone who's had trouble at a border other than the US.
For example, in their codebase they had ambiguity between bytestrings and unicode strings. As Python3 tries to prevent you doing this, to resolve a big footgun from Python2.
The right fix here is to be consistent in your use of strings. Sometimes that is tricky because of how third party libraries have decided to implement their 2/3 compatibility, but it helps prevent shooting yourself in the foot with unicode bugs down the line.
Instagram did not do this. They created utility functions to force their data into the format they wanted at the point it is used. In other places they used tuple() to make sure that map calls that had side effects were fully iterated over.
In short, they had bad Python2 code and now have had Python3 code. Sometimes, at large scale, it's your only choice. But to smaller companies looking at this it's a bad idea. You're setting a precedent in your code that it's okay to make the same mistakes that Python3 tried to prevent.
Secondly, I agree that it's far too much money for a weekender level. Bear in mind that most weekender projects will be using free tiers at various providers. This could easily swamp all other outgoings combined.
If you really do want to capture the weekender market I'd probably suggest cutting the cost to 1/3 of current and billing annually.