hudo

First thing about most HIFI speakers is that they have to be at least 0.5m from the back wall. Otherwise you lose sound stage depth and get bloated bass. Its such a shame to see people giving 5-10k$ on pair of really good speakers and putting them 20-30cm from the wall (i see that ALL the time on various FB groups). I have mine floorstanders around 1.2m away, where they sound the best. Is always a compromise between room and speakers placement.

Its actually Win10 that people hate, dev tools are just fine

Postgrest is RRM actually- rest relational mapper.

My point is - exposing db over HTTP (REST, GraphQL, ...) is bad architectural design and idea.

"Object-relational mapping is a leaky abstraction leading to slow imperative code"

So they added REST on top of ORM, few more layers of data transformation and even leakier abstraction, so poor dev doesn't have to worry about "low level" SQL.

I lost count of how many different libs/frameworks i saw that exposed CRUD through HTTP, all failed miserably, because it is actually very dumb idea.

The whole Metro/Modern UI is in like 90% cases much much uglier than whatever was before, and even after years of using them, I just can't get used to them. Every time I see a dropdown, text box or check box of new Modern UI, I think there's some CSS missing or page didn't render correctly. Looks cheap and ugly.

Then google comes and do some version of Modern UI on web and Android, which looks and feel miles better than MSFT!

> - Allow functions outside of classes

use a delegate for this:)

Btw, for dev on Mac I use Jetbrains Rider, its like VS with Resharper or even better. Its also available on Linux. Otherwise, for smaller (micro)services, VS Code works fine. As soon as you start fighting with Code, maybe your solution is too big?

no response from PM, amazing! I've been MVP for (just) 6y, 2012-2016, and probably replaced that many community PMs, and few categories also, that I didn't know where I belong any more. And last year, when I thought I did my biggest contribution by organizing workshops and meetup talks, writing OSS, and finally got great feedback from real people, not just page views of blog or twitter reach, they called me and said its not enough. And that I can apply next year when I do more of the things they measure, whatever that is this year! I just don't care any more.

What NYT thinks devs are doing in Silicon Valley: AI and machine learning hacking in VR 3D

What devs are really doing in Silicon Valley: debugging yet another "undefined is not an function"

Any known list about migration of tech jobs from London, what EU cities will now be more interesting for software engineers? Im still in Dublin, but on lookout for some other city/country because of crazy prices in Ireland (rents going up much faster than salaries), and stability (not sure how will Ireland handle Brexit since it depends on UK for lot of import/exports).

Try to solve complex architectures that can handle race conditions without some kind of event sourcing, good luck with that

Even measurements on the paper looks great when we talk about how it actually sounds, this review explains it the best https://www.youtube.com/watch?time_continue=12&v=uzbTRMIFL-4

That's the difference with "mainstream" companies (sony, panasonic, ...,apple?) and hifi one (rotel, nad, marantz, ...): sony will probably send the amp/speaker to production after it looks ok in measurements, while hifi companies always listen after measurement, tweak, measure again, listen, ... you get the point.

If you don't have to map to DTO, or domain == dto, then its probably an overkill.

But what if you expose domain model to the view, and view changes some property? Are you 100% it will not be saved to db?

If you change one field in a db, do you have to change domain model and UI also?

Important concept is Persistence Ignorance, and how "far" are you willing to go with decoupling application layer from database and domain model. It really depends on your app, and there's no "one correct way of doing this".

Usage of IHttpContextAccessor is official way on hot to access httpcontext. They (ms team) probably have a good reason why to expose IHttpContextAccessor and not httpContext directly.

Configuration can come from different sources, it can be reloaded, it can be lazy-loaded, there are so many different reasons why config is more like service and not a static variable. It has to be injected. Maybe you're using it in a way static access makes sense, but when you're designing generic Configuration solution, its whole another set of problems, requirements and constraints.

Im definitely stealing some tricks from this list, very useful!

Also, this Cierge thing is great! Didn't even know something like that exists (in asp.net core, except IdentityServer, which more like enterprise solution)

Neistat is a great guy, but I just don't get what CNN expected, whats supposed to be ROI of 25m price paid!?

Most people really don't care if MS knows you opened Code, used it with JS and Python projects, and installed 3 extensions. And yeah, it makes Code much better when MS knows how you're using it, btw

No, it does not kill trust. Maybe only in people who doesn't know how to configure and use CLI tools properly. Just disable this feature and move on!

They want CLI arg to out out, and not environment variable. I personally don't have problems with ENV vars, so don't understand their problems.

1. collecting usage data (which doesn't contain ANY personal info!!) will make .net core better.

2. you can opt-out easily.

I fully support things like this, every company out there is using some kind of feedback mechanism to get insight how are customer using their products.

Not just that, for example GitKraken uses Electron, and consumes ~700MB RAM, compared to Smartgit that takes only 120MB on my machine.

If its called asp.net 7 people would think its backward compatible. And since almost everything was rebuild from scratch, WebForms doesn't exists, WCF also, most important namespace System.Web is gone, it wouldn't be fair to version it with 7. MVC API looks the same, but that's about it, everything else underneath is new. MS went long way to "emulate" old MVC and WebAPI, for easier porting of old apps.

Why's that? IMHO, its finally some good usable .net. Full fx was ok in 2005, but today Core is the proper framework. Sure, tooling is still half broken (only if you try to do some crazy thing), there's small API surface in Core 1.1, but I have few apps in prod already, and development is good and easy, no major issues or showstoppers.

sure, i'm also in Dublin, it's sometimes (well, often. I mean, always) difficult to understand them if they talk fast ... but it's the same case if I visit UK, or I guess any english dialect.

I'm sure she could talk more slowly and clearly and computer would say yes.

Don't really like the article. Like it's written by manager, for some upper manager.

As many of people said here in the comments: 1. cloud is expensive as hell. Its much faster and cheaper to rent some dedicated server. Sure, it can fail since there's no failover/scaleout, but startups should fail fast, right? With good backup and acceptable downtime in case of failed hardware, dedicated hw is good enough for this stage of company development, imho

2. article assumes that building distributed system takes equal amount of time and knowledge as building one monolithic app.

3. you replaced one sys admin with dev ops. Sure, dev is dev ops, as I was dev and sys admin before, so don't see any difference there.

4. vendor lock in. Looks like at the end of the day, only AWS profits here (gold rush and seller of shovels 100+ y ago, anyone?)

5. let me just add this one; unpredictable cloud behaviour. Basically cloud providers forces you to scale out from beginning, since services can go down anytime, network can drop, etc. So instead of delivering features you're deep in aws metrics and logs, trying to understand why DynamoDb lost some random writes.

With right team, amount of money and resources, cloud makes sense. Same like running on your own rented dedicated/vm machines makes sense.

Interesting, I still haven't seen Irish pub with loud music. In the evening some of them transform into night bars, so I don't count those. I live in Dublin btw

And im getting bunch of 404s for .net docs. Which means its not really a serious project

But for .net the good ones are (from top of my head):

Jimmy Bogard (marten, mediatr, general architecture)

Jeremyd Miller (structuremap)

Jeremy Skinner (fluentvalidation)

K Scott Allen (typescript and genereal .net core)

Mike Hadlow (.net core)

Mark Rendle (.net on linux, funny guy)

Jonathan Channon (nancyfx)

Brad Wilson (xunit)

Damien Edwards (.net core)

Rick Strahl (.net core)

Jon Galloway (javascript and .net)

Leon Bambrick (very funny guy, knows everything)

its mostly web server benchmark (Kestrel in .net case). So receiving bytes by OS kernel driver, passing them to http server, then to the app, app replies with simple response. Not so relevant to most of us IMHO, since our app code is like 10000x slower than web server can handle, but nice to see .net in first 10:) By looking at computation speed (chess engine?), i would say c# beats Js easily there (should be on-par with Java, but Java has some neat tricks in JIT and can be faster in same cases).

But definitely new .net core feels so much snappier than full fx. Im currently porting few apps (they are simple, no big libs), and so far everything works fine. It took me awhile to catch up with MS changes, since they're iterating little bit to fast... Using full vs 2015 update 2 + r#, and little bit of vs code on ubuntu (r# is still huge productivity booster, i can't switch to vs code yet). Also waiting for Jetbrains Rider, which will bring r# to all platforms!

project.json is still official way of configuring the projects. Dotnet cli uses that, msbuild is not there yet i think. Empty project is done with "donnet new", and it's really small and light ...