StreakyCobra

I don't understand why people always want to tell other people how to behave. The change was decided by Arch developers and impacted only the Arch distribution. Arch developers and Arch users did their job by adapting the Arch packages to work with this. I don't see any problem. If users don't like this choice, they are free to use any other distribution. If software developer don't like this choice, they are also free to not support Arch. And even this is not a problem most of the time because Arch users are doing the effort of adapting and packaging applications themselves on AUR.

Archlinux made the switch in 2010 [1], and this PEP was created in 2011. [1] https://www.archlinux.org/news/python-is-now-python-3/

Fair point. But Archlinux made the switch in 2010 [1], and this PEP was created in 2011.

[1] https://www.archlinux.org/news/python-is-now-python-3/

For a "similar" approach, I would opt for a slackware or a gentoo.

I understand that some people would like to keep Arch 32 bit for their use cases. But as any open source project, the developer are mostly working on it on their spare time, you can not force them to work on anything. Having followed a little bit the discussion on the mailing list [1], I don't remember having seen a lot of objection among the developers. Also, they encourage the creation of a community around i686 [2]:

     However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The arch-ports mailing list and #archlinux-ports IRC channel on Freenode will be used for further coordination.

So if there are people willing to do the job, Arch will still be usable on 1686.

[1] https://lists.archlinux.org/pipermail/arch-dev-public/2016-D... [2] https://www.archlinux.org/news/phasing-out-i686-support/

So to avoid re-opening the debate of Python 2 vs Python 3, let's take this point of view: The Python 3 language may, or may not, have been an improvement, and the transition from 2 to 3 may, or may not, have been done correctly. Everyone has its own opinion on this. But at the end this problem concerns the Python community.

From the Arch developers point of view, the Python developers decided to release a new version of their language. They were going to support python 2 for a while, but the direction that the language was taking for the future was Python 3, so one day or another Python 3 would become the standard, so doing the switch was the good decision.

As said by @tbranyen the work of adapting shebangs have been done on the Arch side anyway, so I don't see a problem for people developing their projects in Python. Also Arch users are mostly power users (you need to understand quite a bit about linux to install it) so they are usually able to handle python 2 vs 3 errors quite well, especially as it is known than Arch use Python 3 by default.

Indeed.

There are other distributions better suited (even specialized) to be run on old hardware.

It is one of the reasons that makes me love Arch: developers are pragmatic. They were always in the early birds for taking decision about the future, like switching to Python3 as default interpreter system-wide, embracing the change to systemd, and now this.

The rolling release aspect imposes to stay as close as possible to upstream versions because upstream does not wait on Arch to update their dependencies to newer libraries versions. This, plus the fact that Arch tries to stay as close as possible to vanilla upstream packages (i.e. less changes as possible), force them to be pragmatic about their choices. They prefer to embrace a change directly when it is happening, encouraging at the same time to contribute upstream for helping them make the transition, instead of trying to maintain a legacy compatibility that can only get worse with the time.

For me the picture is simple here: Arch is mostly used/oriented towards personal computers of power users, and most - if not all - of them are on 64 bit for years now. Instead of wasting efforts to maintain 32 bits compatibility, they prefer to drop it. Side effect will be that people will be encouraged to get a modern computer if not already.

Yes, I know this is possible, and as I mentioned in a response to a comment below:

«I thought about doing so with owncloud, then I decided that paying when I reach the syncing limit would be a nice way to encourage the project.»

So if I understand you right, for syncing your bibliography you changed the "Data Directory Location" to a synced Box folder (a dropbox-like system)? I thought about doing so with owncloud, then I decided that paying when I reach the syncing limit would be a nice way to encourage the project.

Papership and LiquidText looks really nice, I would love to see such applications for Android. But I presume Apple is a more interesting platform as many researchers are on MacBooks. I suppose this is because researchers have really few spare free time and they don't want to use it fighting against the (linux) machines.

I have taken ReadCube into consideration, but quickly dismissed it because A) there is not Linux support [1]; and B) it is not open source.

The open-source side is important for me because the data accumulated in these software is really valuable. If one day the company has to close, you may be stuck without access to your data. With open-source software I'm at least sure to be able to continue running the latest software version on my own, and a community can start to take over and maintain it. Also the way data are stored in the computer can be deduced/found in the code, allowing to make exportation/importation to other software easier. I don't mind to pay for a good software – like I'll probably do with zotero for storage when I'll hit the memory limit – but it has to be open-source.

Except this the concept looks quite interesting and the UI seems nice. The only additional feature (in regard to my setup) that I can see on the homepage is the recommendation system, that can be quite interesting though.

[1] http://support.readcube.com/knowledgebase/articles/242873-ca...

The device? My laptop.

The setup on my laptop:

- Zotero (https://www.zotero.org/) A software that allows you to easily keep references to academic papers right from your browser. Available as standalone app with multiple browser extension, or directly integrated into firefox. When you are on a paper's webpage, clicking on the button extracts its information, its PDF (if available) and do a capture of the webpage and store everything structured. You can then copy citation directly from zotero, generate a bibtex file, or use libreoffice extension. It also allow to sync between computer up to 300M, and extending the storage is quite cheap.

- Zotfile (https://github.com/jlegewie/zotfile) An Zotero extension that monitor the download folder to let you attach downloaded PDF to existing entries. It also rename PDFs with the pattern you want. And the killer feature: It is able to extract what you electronically annotated on the PDF (Highlights, comments)!!

- Okular (https://okular.kde.org/) For reading and annotating PDF. Straightforward use, nice annotations tools (F6 to open, double click items to make them permanent). Ctrl-S to save the annotation to file (otherwise stored somewhere in the user home file).

All these are open source software and are available on Linux!

This repository gives a nice overview of existing financing solutions with some pros/cons. It's oriented towards open source projects, but this doesn't mean it can't apply for other kind of projects.

https://github.com/nayafia/lemonade-stand

> But seriously I can't use `<SomeThing onClick={this.handleClick}/>`?

Give a try to Vue.js, you can do exactly this. This framework reconciled me with frontend development after I discovered it on HN. Let's say you want to build a custom button with a special functionality and reuse it, like a button that logs when it has been clicked. Simply create a component like this (it's almost self-explanatory):

    <template>
        <div class="colored-box">
            <p @click="logClick">{{ text }}</p>
        </div>
    </template>

    <script>
    export default {
        name: 'LogButton',
        props: [
            'text'
        ],
        methods: {
            logClick: function () {
                console.log('The button "' + this.text + '" has been pressed"')
                this.$emit('click')
            }
        }
    }
    </script>

    <style scoped>
    .colored-box {
        background-color: red;
        border: solid 1px black;
    }
    </style>

There are 3 sections in the file, one for the HTML template, one for Javascript code, one for CSS style. All this belongs to the same components, so the methods you defined in the javascript code can be called directly from the html template as you wanted.

Once your component is ready, you can use it in other files, and in a damn simple way:

    <LogButton text="Delete" @click="…" />

It would be nice to at least provide a way to try it outside US/CA, like giving a link to an APK here, especially because it's a «Show HN» what means you want to show your product to this community. I wouldn't be too concerned about negative reviews as A) non-hackers will not find this link and will not know how to install it anyway; and B) most people here would be smart enough to understand it's a prototype that is currently limited to one culinar culture, if you explain it while providing the link. This would avoid the frustration that probably more than half of the people are having here when wanting to try your app.

It looks damn cool, but I'm really sad to not being able to try it just because I don't have the right IP address :-(

I bought 3½ years ago the (quite expensive) Samsung Galaxy Note 3. I bought it for three reasons: 1) It was a mainstream phone, so geek/hackers will buy and use it; 2) It is possible to change the battery; and 3) It has good specs.

I couldn't be more happy with this choice today, as:

1) Thanks to some passionate people [1] who are spending their time to port new Android versions to it, I already have Android Nougat on my phone, before most other devices on the market. Quite impressive for a 3½ old phone to still have geek/hackers working on it.

2) Thanks to the replaceable battery, I just got my phone a new youth. 48h of uptime easily, up to 72h if I don't use it too much.

3) I paid the price for the specs back in the time, but 3½ years after this phone run really smoothly without any noticeable slowness.

If I clean the screen, you will swear that this is a brand new phone: no marks (even if I stopped using a case 1 year ago), a more recent Android version than most of the phones sold today, a good battery life, running a smooth interface without any glitches even on the most demanding apps/videos and having all the features that are built in phone nowadays (NFC, IR, GPS, Accelerometers, Compass, Camera, Sound, LEDs), you can even consider that it has more than them thanks to the stylus and "wacom" screen that are just amazing.

I think I love my phone, let's hope that will continue!

All this to say that even if your phone is not going to have the Nougat update, if you are nerdy enough you can look on xda-developers to see if someone has ported it to your phone, who knows?!

[1] https://forum.xda-developers.com/galaxy-note-3/general/rom-c...

Yes it is a little bit of that.

In industry goals are maybe poorly defined, but at least you have directions, and people that can answer the questions you may ask. If the contract is about creating a website, at least you know what you are going to achieve, even if you may have to fight with the customer to understand what he wants/needs on this website and what problem he is trying to solve.

Using the image of pushing the boundary: Doing a PhD is like wandering within some heavy fog. You want to push the boundary, but first you have to find the boundary. You don't know in which direction is the closest boundary as you can not see further than 10 meters from you. Maybe also the closest boundary is on top of a 8000 meters high mountain that you don't have the capacities to climb. So at the end you spend you time trying to figure out in which direction to go. Some PhD students may have supervisors that are guiding them through the fog, as they already explored the area and know it, but some other are on their own, trying to figure out a boundary to push that is accessible for them.

Situations of all PhD students are probably different, but this is my feeling about it.

> The reposter still doesn't link back to the actual article as requested, though that's just a "please" clause. I guess naming (and even linking) the author and giving the title suffices to satisfy the attribution clause of the license.

Indeed, I thought there was a link to the blog post, but there is not any. The situation is different than before though, as the real author is now at least credited.

I don't know if the link above has been changed by mods or was a mistake, but here is the link to the original article:

https://thebittheories.com/masters-versus-ph-d-2b26ef33f883

The original content is licensed under a CC license [1], and now (it probably has been updated) the reposter is respecting the terms of it:

    1. Please attribute the original work to me (Matt Might) and link back to this page in your reproduction: http://matt.might.net/articles/phd-school-in-pictures/ as The Illustrated Guide to a Ph.D.

    2.When you attribute, please also link my name, Matt Might, to http://matt.might.net/

    3.And, don't forget the "Keep pushing," at the bottom!

So I don't see any reason why the original link can't be shared in thread's comments, especially because people should be allowed to see by themselves the original article in order to forge their own opinion on discussions happening here.

[1] http://matt.might.net/articles/phd-school-in-pictures/#licen...

> 4. Ability to work with poorly defined goals.

This is the most difficult part of a PhD for me.

Note: This quote is from the article on which this thread was pointing to before it has been changed by mods. https://news.ycombinator.com/item?id=13382223

For the weather it's not that bad in general, and if you pick the best canton in Switzerland (Valais) {{Citation needed :-) }}, you will have more than 60% of sunlight [1]. The place is also really beautiful [2] and have been in the «52 Places to Go in 2015» [3]. Only drawback, it's a quite rural area, so not the better place to find jobs in IT in Switzerland.

[1] http://www.meteosuisse.admin.ch/product/output/climate-data/...

[2] https://www.flickr.com/search/?text=valais

[3] http://www.nytimes.com/interactive/2015/01/11/travel/52-plac...

Hi,

Reading your situation, my first thought was to consider the "Personal bankruptcy" [1]. I don't know what this would imply for you, if your country has such a system, or even if it is a good idea in general to go for this. Probably any other solution to get money would be better, but if you don't succeed or get into an even more difficult situation, this may be an option to consider.

Good luck!

[1] https://en.wikipedia.org/wiki/Personal_bankruptcy

Discussed there: https://news.ycombinator.com/item?id=13175388

While I appreciate the effort of putting it open-source, and even more to do it on GitHub, I hope they will hire someone who knows how to use Git/GitHub, like using tags for versioning instead of repository name [0], or using meaningful commit messages [1].

For the future let's see how they will manage external contributions. Opening the code for transparency is a good point (even if this still doesn't ensure you that the same version of the code is running in production on trusted hardware), but doing this on GitHub will certainly bring some contributions. Will they refuse everything? Or accept external contributions? Will they use GitHub as the central development process? If not how are they going to handle the development in intern in regards with external contributions? Also are they going to do all commits with this dedicated state-account? Who will be part and what would be the process for reviewing and accepting external contributions, to be sure they are not adding backdors purposely desguised as mistakes? Having a state starting to work on open-sourcing such a sensitive software in Switzerland opens a wide range of interesting questions. Maybe, and probably, this has already been discussed in other countries or even other part of Switzerland, but in the state of Valais (Switzerland) this is at least not the case.

It's not the first project under state control in Switzerland that is on GitHub. I'm also aware of geo-admin [2] who have their sources there. As far as I saw, they are handling GitHub much more professionally.

[0] https://github.com/republique-et-canton-de-geneve/chvote-1-0

[1] https://github.com/republique-et-canton-de-geneve/chvote-1-0...

[2] https://github.com/geoadmin

Indeed, so it's probably just be my own curiosity that leads me to find this priceless.

Projects should not try to start that big directly. Remember the Linux Kernel first announce: «I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.». It takes a lot of year to arrive to the project it is now. Another example is Spacemacs, now with close to 10'000 stars on github. It took 2 years of contributions from the author before any external contribution has been made (https://github.com/syl20bnr/spacemacs/graphs/contributors).

But anyway it's priceless to have in mind the big pictures and all steps needed to build a strong community for an open-source project right from the beginning :-)

This has already been posted on HN more than one and half years ago [1] and the first edition get back to 2005. It contains updates up to early 2016 as mentioned in a few paragraphs. This book is a classical and a must go for anyone wanting to start building a strong open-source community. It covers a wide range of topics:

- Getting Started (Name, Mission, Documentation, Hosting, Code of Conduct, …)

- Technical Infrastructure (Web site, Mailing list, Version Control, Bug tracker, IRC, Wiki, …)

- Social and Political Infrastructure (Benevolent dictator, Consensus-based Democracy, …)

- Participating as a Business (Contracting, Funding, Marketing, Organization, …)

- Communications (Common pitfalls, Difficult people, Handling growth, …)

- Packaging, Releasing (Versioning, Branching, Releasing, Testing, …)

- Managing Participants (Community, Transitions, Committers, Credits, …)

- Legal Matters (Licenses, Contributors, Trademarks, Patents, …)

(This list is a subset of the Table of Contents)

It covers nearly every topic that an open-source community can be concerned about, and each section contains valuable thoughts for communities starting to wonder about a given problematic.

I read the first edition eight years ago, and I'm planning to give it another go because I realized that I've forgotten a lot of what I read. Another good excuse to read it again is that the world and tooling has also evolved quite a lot in 8 years (Github was launched 8 years ago!).

Happy reading!

[1] https://news.ycombinator.com/item?id=9323653

Of course not. Our brains evolved in a way so that a smiley appears on brain's scans top-rear point-of-view whenever we are in the responding phase of a math problem solving :-)

Side note: https://github.com/supercrabtree/k is a ZSH plugin in the same register that `exa`.

As you said, something like IPython: https://ipython.org/ipython-doc/3/interactive/shell.html