Todd

She said under Code of Conduct, "This was something I didn't always have when first organizing groups years ago, and I learned over time why it's necessary." I was curious about that and hoped that she would elaborate.

I use a 43" 4k TV as a monitor and it's great. It's on the outside range of size due to the 100 ppi pitch.

You're referring to chroma subsampling. Rtings does a review of 4k TVs that support 4:4:4 chroma.

https://www.rtings.com/tv/reviews/best/by-usage/pc-monitor

This page also has a link to their subsampling article.

The article says:

In 1970, 61 percent of Americans belonged to the middle class, said Kochhar, “a clear majority.” Using Pew’s methodology, that figure now hovers around 50 percent nationally.

The Anabasis by Xenophon can be read in the original, with translations on alternating pages, as in the Loeb series. There are also interlinear translations available, such as this one: https://archive.org/details/anabasisofxenoph00xenoiala/page/...

As many people are pointing out, they has been used as an alternative singular pronoun for a very long time. For those who think that these things are unacceptable, one only has to look at other Indo-european languages.

German has sie, which means 'they' (in addition to 'she'). However, they also have Sie which means formal 'you'. This is the same mechanism at work, albeit formalized and thus further along the path to acceptance.

French has a more recent example. The pronoun on means 'one', in the third person singular, gender-neutral sense. In recent history, it has been transformed to take on the sense of 'we'. The motivation, as with many things French, is to shorten words and to make things less formal. The on conjugation of verbs is more brief than the nous (we) equivalent.

These languages have re-purposed pronouns in a natural way, and have accepted it--even formalized it in grammar books. English needs to do the same.

It's because that's the way English verbs are conjugated. English actually has a very simple way of conjugating (regular) verbs. Most of the complexity of the ancestral Germanic has been lost. Contrast that to other Germanic languages. Swedish present tense, for example, is very simple. German still retains a complex morphology.

The only inflection English retains in the present indicative is the -s suffix for 3rd person singular (frog). Third person plural (frogs) does not have an -s.

The -s suffix for noun plurals, and for possessives (vestigial genitive case), add exceptions that make learning English a little harder.

Edit: grammar :)

Comcast Business is bad near Seattle

It does make it much easier to get going. Most of the packages you expect to be able to use are there. This only becomes an issue if you want to run cross platform. Once nice thing they added recently is that they issue warnings if some of those packages depend on Framework, which helps.

Here's the associated submission:

https://news.ycombinator.com/item?id=15009929

Another great polyglot was Sir Richard Francis Burton [1]. Not only did he speak more than 20 languages, but he led an incredible life. Edward Rice wrote a great biography [2] (although I read the earlier edition). Burton himself wrote a great deal as well [3].

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

[2] https://www.amazon.com/Captain-Sir-Richard-Francis-Burton/dp...

[3] https://en.wikipedia.org/wiki/Richard_Francis_Burton_bibliog...

Yes, exactly. It's great that we can continue along editing and committing. The freedom that DVCSs bring has really changed the world of development. However, feeling the pain of not being able to access other repos shows both the value that Github brings and also the downside of siloed services.

A paper that covers some of the data structures used in editors is:

https://www.cs.unm.edu/~crowley/papers/sds.pdf

The gap buffer, in particular, is a great example of a simple yet powerful idea that is perfectly suited to the problem domain.

I have kept one off and on. I like writing using pen and paper. Given that I type much more quickly and I'm at a computer all day, a file-based journal is more pragmatic.

I wrote a simple script 14 years ago to automate the organization for me.

http://pastebin.com/pnWQemAf

I just alias a simple one letter command to "jour.py work" or "jour.py blog" and running it will open a file with a date-based name in my editor of choice. Re-running it on the same day gets me the same file.

This method has the advantage of a very organized, timeless format. The disadvantage is that it's on my local machine. Of course, a cloud based file store could be used, but there is no default encryption and there is no mobile option.

I would pick a set of technologies that you want to learn. This will require a bit of research, of course. It's a bit of a personal decision, based on your predilections and your past experience.

There is a ton of activity in the space, of course. I would first glance at the ECMAScript efforts of late (ES6 and ES7 in particular). You'll probably need to use Node.js, since it tends to be the center point of JS development, regardless of the tools and frameworks you choose.

The first piece is your build tool. Grunt and Gulp are the two top build tools. Gulp is more recent and seems to have more uptake. If you haven't written a build script (e.g., gulpfile.js) I recommend building one up from scratch rather than using someone else's. You could use others' for examples of what to do, but build your own from scratch according to your needs, as you go. You'll learn more and understand the whole thing that way.

The next choice is whether to use a transpiler or not. The two biggies are Babel (ES6 transpilation to ES5 or ES3) and TypeScript. You can skip this step at first, but it will be a foundational aspect to your build, so don't wait too long. If you do skip it, loop back once you've made your other choices.

The final big choice is framework. The big ones right now are React and Angular 2. There are many others, of course (Vue, Inferno, ...). You might try a few efforts here to learn about them if you don't have a clear initial default choice.

There are secondary choices depending on which main framework you choose. For example, if you use React, you will likely need a client-side store. Flux used to be the default. Now it's likely to be Redux or, more recently, MobX.

There hasn't been a better time to be a JS dev. There's still a lot of churn, but there's also more stability than there has been in the past few years. You can stick with technology choices for a year or two without major disruption if you make course corrections. Good luck!

I went through a similar phase when I was younger. I had been involved with amateur radio since I was 13 and everything in my life pointed to EE at university. By the time I got there, I didn't see the point anymore. I no longer found it interesting.

Shortly thereafter, I rediscovered programming and I've been doing it ever since (20+ years). In hindsight, I think I had just gone through my first bout of burnout. I still find electronics interesting and enjoyable. So burnout may be one aspect of what you're experiencing.

Since you're an extrovert, you have a natural propensity that many people don't have in this industry. That can be a superpower for you. You might excel at giving talks, communicating with other teams, managing groups, and the like. The fact that you enjoy development and have put in the time means that these activities won't be vacuous.

The feelings of exasperation that you have are similar to what many others--novices and veterans alike--are feeling. Things change quickly in this field. Many others have written about how to cope with this. It's a real thing but something that can be mitigated and gotten past.

You might consider taking a step back and recharging. The New Year time frame is an excellent time to do so (generally speaking). Think about a few goals that you may want to focus on this year. If you pick a project, choose one that means something to you. It could be one of your own or someone else's. We live in an amazing time of open source and collaboration.

The main thing is, don't worry. You've got plenty of time ahead of you to pick your path and make things work. The fact that you're reaching out and searching for answers is a great indicator of future success. Just keep moving forward.

This is the biggest design flaw with this laptop. It is a very unflattering angle and makes the video essentially useless. It's the one reason I can't recommend it to people (or I recommend it with a caveat, if they use the camera often).

This is from 2012. Here's the original link:

https://channel9.msdn.com/Blogs/Charles/Erik-Meijer-and-Robe...

First, you're comparing two different domains. App developers (whether mobile, web, or some other environment) live at the top of the stack. As such, they must wrangle many disparate frameworks and libraries to achieve their goals. Framework developers can focus on a narrower set of concerns--albeit sometimes quite deep.

I would suggest that you stop comparing yourself to them and their achievements. Rather, use their example as a starting point in your pursuit of improvement.

Many others offer good advice here, but one of the cornerstones is to look at what others are doing--often and deeply. Many have asked, "How do I become a great writer?" The answer invariably is, you must be a great reader. You need to read A LOT.

The same goes for math. You must solve problems. That's the other half of the coin. You need to do. So pick a problem that hasn't been addressed. Maybe there's something you haven't found a library or framework for. Take the opportunity to build it, package it, and open source it. You'll see that the set of concerns is different from that of an app developer.

Edit: typo

One advantage of storing multiple schemas in one database is that a connection can be shared (assuming a shared authentication strategy). This is because, as mentioned in the article, the switch to one schema vs. another happens after the connection. This can make it easier to pool connections and to share servers across tenants. A tenant_id approach gives the same benefit without the isolation, but a separate database (even on the same server) doesn't.

Edit: typo

I think they each have their place. More and more of what I do involves rich client work and so I often need Node just to build the client.

For API work, I think .NET is just getting better and better. Now that it's cross platform with Core, there are fewer impediments to choosing the right tool for the job.

With my projects it comes down to whether I use MVC for a more server-focused app or Node for one that's more client-focused. If you do use Node, you have the option of building universal/isomorphic apps. Of course, it mainly comes down to how you like to build your server side pieces, and which environment and ecosystem you prefer.

My current project is mostly MVC (we haven't moved to Core, yet) with a WebAPI piece, but I still use Node to build our rich client pieces. They're built with React and TypeScript. This allows us to continue building primarily a server-side app, while gradually migrating to more of a rich client approach.

The downside with Core is that it's still a work in progress. They've just released 1.1 but tooling is still not quite there. It might be closer when VS 15/2017 is released. One big piece is their move away from JSON project files back to a more flexible XML-based csproj model. They should be there soon. It's just indicative of growing pains.

The other big thing for me is EF7/Core, which is a rewrite of Entity Framework. There's a lot to look forward to here, but it's not at parity with EF6. If you're starting a new project, it's probably OK. If you have to migrate, it could present serious pain. It's the primary reason we haven't been able to migrate to Core, yet.

Regardless, if you used to use .NET and you haven't tried Core, you absolutely should. You don't even need VS. You can run VS Code and you can develop on Win/Mac/Linux/+ and you have the same choices for deployment. Also, as others have mentioned, their new Web server, Kestrel is also getting very fast.

That was well done. Time lapse, yes, but time lapse focal length changes and from multiple perspectives. Some shots over the course of days.

One thing that caught my eye was the strange phrase trop va qui dure, which I was having trouble translating (I'm not a native speaker). I felt better when I looked at the Wikipedia page which said that the origin of the name remains mysterious.

https://fr.wikipedia.org/wiki/Rue_Trop-Va-Qui-Dure

The road was also called the Road Along the Seine and Misery Valley. It disappeared in 1813 when they demolished the Grand Châtelet.

You can still see traces on modern Paris--places like the Rue St. Denis. There are also remnants of the Grand Châtelet in place names, like the shopping center (more like a mall) called Châtelet - Les Halles not far from its namesake.

My guess is that it's because PBKDF2 is provided as part of the .NET Framework.

Related book to be published soon:

https://www.amazon.com/Designing-Your-Life-Well-Lived-Joyful...

Yes, they've taken pragmatic steps to deal with it, given the current situation. It seems that there may be another aspect to basic income refusal that isn't immediately evident. Perhaps the suspicion that is prevalent here for reasons related to local culture and customs are actually more universal. Maybe there is a way that UBI can be tweaked to accommodate for that. I know that one of the cornerstones of UBI is unconditionality. However, it may need to be adjusted if this is a more universal phenomenon.

I meant profit in non-monetary terms, but in terms related to the experiment. When you run an experiment, and you get a result you didn't expect, there may be a new discovery or a silver lining if it's an undesirable discovery.

This seems like the kind of surprising result that the scientific method begs for. Instead of trying to understand it, or profit from its prevalence, the organization is attempting to reduce it.

It doesn't seem likely that this type of thing will be a long term concern, but perhaps something can be learned about how society adapts if a significant subset decline the payment.

Where are you located? Maybe you should add a throwaway email to your profile so people can contact you. It might also help if you mention the area that the invention relates to. If someone with an interest in that area happens on this post, it will make it more likely that they will reach out.

Also, if you're trying to contact VCs, you need a warm intro from someone they know, so tap your network.

I just installed D4W a few days ago for the first time. It's been great. It's a seamless experience on W10 Pro with Hyper-V. I've used VirtualBox a lot and I like it but I always have to fuss with the network bridge and such. With this, it's hard to tell I'm even using a VM. Their network port mapping is seamless.

FYI, I was using rc4 and I didn't see any information on how to upgrade (should I uninstall first?). I ran the release setup and it did an in-place upgrade, deleting earlier components and such.

This was demoed today on the ASP.NET Community Standup at http://live.asp.net.