Recent submissions

Comment · 10 years ago
Comment · 10 years ago
It was the original title.
Comment · 10 years ago
> Are they really "so complicated", or is it just a large amount of options, many of which might actually be ignorable for the task you're doing, that contribute to such an impression of complexity?

Apache's library called it HSSF, Horrible Spreadsheet Format. You make the call.

:)

Comment · 10 years ago
Please stop with the razors. Someone will get cut.
Comment · 10 years ago
Comment · 10 years ago
What about the following text in README:

'If you are building from source then you get no support and must work within the restrictions specified of the fair source licence (see LICENSE.txt for details). To purchase support see https://searchcode.com/product/#downloadlinks'

And what about:

'Use of this software is governed by the Fair Source License included in the LICENSE.TXT file'

No period there at the end, but that seems to indicate to use the LICENSE.TXT.

And then, even worse:

'In order to deal with the case of my death or this software becoming abandoned it has a time-bomb where the licence will change exactly 3 years after the publish date of a version release. This means that if version 1.0.0 was released on 1 July 2010 then it can be taken using the listed alternate licence on 2 July 2013. This licence, version and time is all specified below.'

There is no definition of what 'software becoming abandoned' (Which 'software'? What does 'abandoned' mean?). There is no definition of what 'it can be taken' means. The example date is one day more than three years and the dates given as examples could confuse the date intended for expiry. There is no definition of what should be used as the 'publish date of a version release'.

While these things may seem common sense to a developer, they should have a clear legal interpretation.

Comment · 10 years ago
I'm not sure if this will work as it is currently, and here's why:

https://github.com/boyter/searchcode-server/blob/master/LICE...

Clearly shows that it is released under the Fair Source License, version 0.9 with no mention of license termination and restricted rights. It is NOT free.

https://github.com/boyter/searchcode-server/blob/master/READ...

then states:

'After the following date 27-August-2019 you may choose to use this software, version "1.2.3" or "1.2.4" under the GNU General Public License Version 3 with terms specified at https://www.gnu.org/licenses/gpl-3.0.txt'

This is so wrong. Not that it is GPL, but this both contradicts the license and states that you "may choose to use this software..." under the GNU GPLv3. Also, the missing comma after "1.2.4" is a mistake in grammar.

I'd say, as-is, you should consider this licensing unreliable. Yes, he posted in his blog stating his intention, but as it is now, it would appear that if a ruling had to be made on the actual license, it could very well be that the only valid license is the one in LICENSE.txt.

Since that is unclear, though, if I were a user and cared about the license, I'd get a good lawyer to figure this out before making any assumptions.

And, I would suggest that he get a lawyer to help craft the required changes to his license.

Comment · 10 years ago
> The entrenched parties would have had a list of approved questions to avoid such a mistake

Not knowing Syria is a huge problem for an incoming president.

Having a warrant out is not something that I would take lightly in someone who aims to be commander-in-chief.

Comment · 10 years ago
Comment · 10 years ago
Comment · 10 years ago
I'm an introvert and tend toward reclusion, but still think that reclusion can be bad. We should interact with others to help them and to be helped IRL.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton