pseale

First, let me just say that this seems great. It looks like a perfect way to use reasonable defaults (project name, Version) and use the existing `dotnet publish` infrastructure to make containers. And I love how the blog post has both a simple CLI example, and a GitHub Actions yaml example! So thank you.

Now for the problem:

I still don't understand why other people compile dotnet projects in containers. Today, we have a many containers built on a monolith, and it looks like if I make containers via `-p:PublishProfile=DefaultContainer`--for example, 20 containers--then that CI build is going to compile our codebase 20 separate times. With `-p:PublishProfile=DefaultContainer`, the long build is mostly duplicated in each container. Right?

So I have one major problem preventing me from adopting this: it's compiling in the container, which balloons our build time.

It's entirely possible I'm missing something obvious or misinterpreting the situation, and if so, please let me know. I'm mostly immune to feeling shame and appreciate feedback.

This is like opening a time capsule and examining all the little details. Almost more interesting than the barebones, locked-in-time product page for a paid C compiler, is the locked-in-time cgi-bin-powered shopping cart page at http://www.safepay.net/cgi-bin/shop/cart.cgi?db=products.dat... (note it's an http link).

There's a whole host of old-school relics here--it is truly a blast from the past: paying separately for a debugger, paying for specific libraries, videos available on DVD.

It's really hard to express how deeply internet access has changed the landscape of ... well, everything, but in this particular case, the programming ecosystem. gcc probably existed back when I bought this compiler, and probably so did Borland's excellent pre-internet-era IDE, but I didn't know that. And so I bought this one.

A reasonable high-enough DPI option I've been watching for a while is a 55" 8K TV. We're close to the 8K utopia!

- HDMI 2.1 can push 8K @ 60Hz over a single cable (though I am told the colors are not full range? https://twitter.com/MaratTanalin/status/1426726300585185284 - "Afaik, 8K@60Hz via HDMI 2.1 is only possible with either DSC compression or chroma subsampling — both are lossy.")

- A 3090 can push the pixels

- 8K TV prices have come down to ~$1500-$2000 - In theory, some combination of Game Mode and/or manually turning off all forms of picture post-processing can get you into good-to-good-enough input lag

If you want to wait for monitor manufacturers to manufacture 8K monitors, well, while it's inevitable, it'll be a while. But for the bold and stout of heart, for those willing to take risks, a new adventure awaits you. 8K

I hope people don't actually believe PowerShell is NIH.

PowerShell had good reasons to exist in 2006, when it was released to the public. LINQ didn't exist yet, most of the "Windows scripting" took place via VBScript files and WMI, and dinosaurs roamed the earth.

So PowerShell was created to be a "scripting language for Windows".

PowerShell has a lot of great features specifically created for use in the shell, and some ok features (like easy COM integration) that were great in 2006. If you don't know what those are, I guess you could draw the conclusion that it's just another .NET language.

HISTalk (a website devoted to healthcare IT) has its take on this article: http://histalk2.com/2014/10/03/monday-morning-update-10614/ (browse down to the "Other" section)

Here's a glimpse of what they have to say about the Atlantic article:

Author credentials are fair game if you’re going to editorialize, so let’s check hers: an intern until 2010, moved down from global editor to staff writer after 10 months in the higher position, wrote about home design and architecture, and listed her most recent accomplishment on LinkedIn as, “Talk about beards on the radio.” Nothing makes me angrier than people who’ve never spent a day working in either IT or healthcare blasting out their entirely unqualified opinions in passing themselves off as authoritative.

Anyway, read the HISTalk article for an insider take.

Would you actually recommend anyone learn MUMPS for any reason besides job reasons?

You are applying your YC bias to the word 'incubator'.

in·cu·ba·tor/ˈinkyəˌbātər/

Noun:

1. An enclosed apparatus providing a controlled environment for the care of premature babies. 2. An apparatus used to hatch eggs or grow microorganisms under controlled conditions.

Thank you. Outlook 2007 and 2010 have a) flags, b) user-taggable-color-coded categories, c) an extremely usable ToDo bar, and d) Xobni and a million other plugins that attempt to prioritize your incoming mail automatically.

I'm not saying Outlook works for me (it doesn't), but it's annoying that the author pretended Outlook doesn't exist, and essentially proposed his version of Outlook as a solution to the "problem".

True art is the Underhanded C contest

http://underhanded.xcott.com/

Related: you can't create filenames in DOS reserved by devices.

http://wiki.answers.com/Q/Why_can%27t_you_create_a_folder_na...

Nope. At work we have a similar setup.exe file. The setup.exe is a bootstrapper that installs prerequisites first, then runs the ClickOnce installer which is separate.

A lot of people in the comments here miss the context: this was written by Microsoft ecosystem developers.

Some of the items on the list specifically target Microsoft MVPs and Regional Directors, the shots at "snacks" and "T-shirts" aim at Microsoft community events, and the rest target standard corporate development dysfunction.

If there's one positive takeaway from this post, it's the bit of the end that warns you to treat your 501 teammates well.

If you haven't even seen Windows 8, please don't comment on it. It's clear from even a quick look at Windows 8 what awkward transition between "tablet" and "desktop" he's talking about.

I blame XAML, and I'm justified. Some of my teammates here have changed Visual Studio to open XAML files with the XML editor, which means * Visual Studio no longer crashes all the time, and * they lose all XAML intellisense.

I choose to keep the XAML editor for its usefulness, but I run Task Manager (well, Process Explorer) open in the tray at all times to monitor my CPU. If your CPU spikes while you're doing nothing, it's a good sign that Visual Studio may crash.

And as everyone else says, it's rock-solid while doing web development or anything not involving XAML.

I've worked as the IT guy in a hospital, and have talked to our "finance guy", and he says the same thing--outpatient surgeries and childbirths pay for Medicare (in)patients and the ER.

And yes, there is inefficiency unrelated to Medicare, and yes, I've seen the anecdote about how doctors who own an MRI machine refer patients to get MRIs six times more frequently.

But Medicare underpaying, alongside what I remember hearing was a "bad payor mix" from ER patients, hurts.

If you're truly curious about how healthcare works, follow this blog http://histalk2.com/ and get a flavor for what's concerning IT people (which oftentimes is money).

There you go, no problems then.

If from a developer's viewpoint, XAML looks identical to Silverlight, and there are the same number of people working on XAML for the Windows team as there used to be working on Silverlight for DevDiv, does it matter?

But I bet you're feeling betrayed. I understand. I felt a little betrayed a few frameworks ago. Post-betrayal, I stick to focusing on transferable skills and JIT learn the rest of .NET. I'm on a WPF project now, have not studied WPF deeply.

My advice: if you have any say in the matter, try to work with ASP.NET MVC as opposed to the .NET alternatives, so your skills transfer.

Footnote: I don't know how many worked on Silverlight/WPF/WP7 versus how many work on XAML now. I assume XAML will march on. But no one will care unless/until the Windows tablet is successful.

The 'official toolkit' Metro is XAML + (C++ or .NET or MSHTML5). I've been told by a (true) Silverlight/WPF expert that the Win8 XAML most resembles the Silverlight API.

Silverlight used to be promoted as:

* Flex/Flash compete * Public web compete (I never recommended it for such) * line-of-business (not publicly available) apps * (recent) Windows Phone 7

Silverlight is now promoted as:

* line-of-business apps * Windows Phone 7, but maybe Win Phone 8 will look more like the Win8 Metro XAML (I don't think they've said anything yet)

Metro is now promoted for:

* Win8 tablet apps * Win8 native apps(? who cares I guess?) * possibly Win Phone 8 apps

I don't know what apps you write, so I don't know what your specific roadmap may look like. I've leaned toward recommending web apps over "client" apps for .NET devs the past few years, and will heavily lean that way going forward. ASP.NET MVC skills translate easily to open source/competing web frameworks. WPF or Silverlight developers can't say the same thing.

Hopefully he doesn't mean it just for employees. The Hacker News community has a bent towards "startup = happiness" which I disagree with, but all things considered, is better than the screddit "eSports is important, and it's important to practice Starcraft" bent.

A lot of us are indeed skeptical. MS has a history of doing focused marketing. The ongoing BUILD conference is currently marketing Win8/WinRT.

A past push that sticks out to me most is the "3 pillars of Longhorn (Vista)". The vast majority of "the 3 pillars (WPF/WCF/WinFS/InfoCard)" are now useless.

We should all remember Vista/Longhorn as something that had an equal amount of marketing, but failed horribly. Anyone remember the Windows Vista UI Guidelines? A search box and back button in every application? The sidebar? Have a graphic designer design your application's UI in XAML (oops, they're still trying to push that one)? Maybe Windows 8's new stuff won't fail, but we can't tell at this point. This is also the same thing I say about Windows Phone, Azure and even something as heavily supported as the Entity Framework. You just never know when funding will be cut or if the product will die.

For me, with all this in mind, I do the bare minimum just-in-time learning to keep up with the day job, especially as it comes to frameworks and new product pushes. Fundamentals such as OO concepts or any kind of universal, timeless concepts, I'll study. But I won't bother with buying the newest WinRT book when it comes out because hey, why bother. Even if I do study up on one of these topics, I'll do it knowing that the platform may die at any moment. I'm sure WebOS folk or niche phone developers (Symbian OS?) know the feeling.

The vast majority of .NET developers effectively do the same regarding learning Microsoft frameworks, only they're more quiet or less honest about how little proactive studying they do, and usually won't own up to the truth. All .NET developers are 'behind the curve', at least as the curve is re-defined every new marketing push.

I don't know how best to moderate or otherwise encourage better HN participation (or how to improve forums, or mailing lists, or tweet streams, or whatever they invent or rename tomorrow), but I have a thought.

Can we apply a "who cares?" ethos/filter to our comments? I.e., if I am about to post a comment, before I do so I ask myself "who cares about this comment?" If the answer is Probably Nobody, then I don't post it. Simple, right?

I do this all the time. I probably write and delete five comments for every comment I post here.

A second question to ask the question is, is my comment adding anything to the discussion that isn't already glaringly obvious? If it's obvious, but I want to nitpick or clarify...maybe just sit on it for a while and see if the urge to comment fades?

With smaller communities, we don't have to apply such harsh filters because hey, who cares, there's 10 of us. We can hash it out amongst us. But with a huge community like HN, if 9999 out of 10000 subscribers resist the urge to comment but just one does, that makes what, 50 comments? 500 nowadays? 5000?

What I'm saying is, I think HN comments would be a great deal better off if everyone just sat back and said "hey, do we really need yet another armchair CEO quarterbacking on Monday (I'm not going to bother getting those idioms right) about Steve Jobs' legacy and the future of Apple, from the wizened perspective of another college student (or in my case, .NET dev)?" Even I'm following the Book of Graham and disagreeing properly and writing well-formed sentences and generally making my points clearly, am I just adding noise? Does it matter if anyone reads my comment?

HN would be better if everyone just, just resisted the urge to comment and let the real experts talk. Most of us already do, but there's just too many of us now for "most of us" to be good enough.

Smart Bear does the same thing: http://smartbear.com/best-kept-secrets-of-peer-code-review/ - I received a free (paper) book after attending a session about peer code review.

I still haven't read the book, but that's a whole different discussion.

Thanks for the feedback, I think you've given better feedback than any of my blog commenters or blog-comment-via-new-blog-post responders.

I think I need to add something to my post, because so many people are reacting badly to it.

If it helps, for context, read this article: http://www.lhotka.net/weblog/WhySilverlightIsTheFuture.aspx and then maybe my takeaways #1-4 will make better sense after you see what kind of opinions are normal in .NET land.

Hey everybody.

Please keep in mind that I work with a lot of people who still think Ruby is a toy language and Rails can't scale. This article was written for my audience, .NET developers who have heard of Rails but know almost nothing besides the name.

My goal with the post was to move people who identify as .NET developers, "because we work on the best platform", towards platform-agnosticism. Not to convert them from .NET zealots to Ruby zealots.

Based on how everyone (everyone) has reacted, I worded something badly/messed up the post.

Have a nice day everybody.

This sounds like how I helped my grandma with her Outlook/phone/digital photo woes. With some things (email) she was extremely successful; with others (digital photos, saving attached photos from emails) she remained lost forever.

She could have benefited from a dumbed-down interface for the things she struggled with. Picasa was as close as I could get as simple photo management, but she needed something even more seamless and simple.

It makes me wonder why there aren't more companies creating products like the Jitterbug ( http://www.greatcall.com/ )--for those of you unaware, the Jitterbug is a cellphone with very large buttons and a presumably easy-to-navigate menu system, with concierge operator service for remedial support tasks ("I need to check my voicemail").

Maybe we have tried making extremely simplified UIs for common computing tasks, and failed (Clippy/MS Bob)? Is there an extremely simple photo management app (or something on the Mac) that I'm unaware of?

At some point IT will stop treating crusty enterprise web apps as web apps and start treating them as legacy enterprise apps that run in IE6.

Instead of mandating everyone run IE6 from now to eternity, IT will provide a Citrix link to launch the crusty web app inside the controlled Citrix environment, and allow users to use more modern browsers by default.

Or so we can hope.

A nice fantasy would be that Windows 7 replaces XP as the new "business OS" line for the next decade (XP has served in this role since ~2002). Windows 8/9/onward would then be free to deviate from backwards compatibility in favor of a better consumer (non-business user) experience.

But it's hard to say what will happen.

I only see stories over 100 points via: http://news.ycombinator.com/over?points=100

...except if I get bored on a Friday and look at new topics, which explains how I saw this link in the first place...

Hope for the future: Windows 7 introduced a new hotkey that resizes windows to take up either the left or right half of the screen: WIN+LEFTARROW or WIN+RIGHTARROW.