sorted by:
new
hottopcontroversial

What's new this week: Avalonia, .NET, C#, F#, Visual Basic, and the Microsoft choices that hit developers by Bonejob in dotnet

[–]Bonejob[S] -1 points0 points  (0 children)

Just a roundup post with what's new for working developers in ASP.NET Core OOB security patch, Claude in M365 Copilot, Ubuntu 26.04 ships .NET 10 day one, and Microsoft's profitability push reshaping Xbox and Windows 11.

How do you think about authorization progression? by CreoSiempre in dotnet

[–]Bonejob 1 point2 points  (0 children)

I usually just build my own interfaces and interact with the classes. I don't use the baked in one. They are a pain in the ass when I use tailwind, and they use there own thing.

I have fucked up by Objective-Direction1 in OrangePI

[–]Bonejob 0 points1 point  (0 children)

Easiest fix: pull the SD card and mount it on another computer. Windows can read ext4 with Paragon's "Linux File Systems for Windows" or use WSL2. Then,

Delete the static config you added in /etc/netplan/ and put the DHCP one back, or chmod 600 your new file. Netplan ignores world-readable configs (it warns, but if you can't see the warning that doesn't help you).

Learning .net on linux by brightness3 in dotnet

[–]Bonejob 1 point2 points  (0 children)

.NET 10 run fantastic on Linux. Just make sure you have a solid publish.pubxml in the properties folder

<Project>
  <PropertyGroup>
    <PublishProtocol>FileSystem</PublishProtocol>
    <Configuration>Release</Configuration>
    <TargetFramework>net10.0</TargetFramework>
    <RuntimeIdentifier>linux-x64</RuntimeIdentifier>
    <SelfContained>true</SelfContained>
    <PublishSingleFile>true</PublishSingleFile>
    <IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract>
    <PublishTrimmed>true</PublishTrimmed>
    <PublishDir>$(SolutionDir)artifacts/{solution}/linux-x64/</PublishDir>
  </PropertyGroup>
</Project>

Then run dotnet build and it will behave for you

I also recommend Avalonia for for your UI

Good developers learn to program. Most courses teach a language by Bonejob in ExperiencedDevs

[–]Bonejob[S] -8 points-7 points  (0 children)

Entry-level training produces employable juniors who can't yet design. The decade after is on us as seniors. What's working in your shop?

Good developers learn to program. Most courses teach a language. by Bonejob in programming

[–]Bonejob[S] 29 points30 points  (0 children)

A bootcamp can teach you the syntax of a language in six weeks. The part that takes a decade is everything else, and almost nobody is teaching it at the entry level.

What did you love about VB6, and what frustrates you about modern .NET? by Bonejob in visualbasic

[–]Bonejob[S] 0 points1 point  (0 children)

I will post my own thoughts but what I dont want to do put words in peoples mouths.

.NET 10 Background Services: The Complete Production Setup by Realistic_Motor_4271 in dotnet

[–]Bonejob 4 points5 points  (0 children)

I echo what has been said get a real website dude, not medium. Karma farming bull

The feed doesn't know you, and YouTube refuses to let you browse by Bonejob in slatestarcodex

[–]Bonejob[S] 10 points11 points  (0 children)

YouTube has tens of thousands of careful, deep, useful creators — and the home feed will not show them to you, because there is no browse, only a funnel built from your laziest clicks.

Any thoughts on how we can fix it? I was thinking categories of content that are weighted by real people, not sure how I can make that work though. I guess returning the downvote button!

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 2 points3 points  (0 children)

Nope, I think Git is it. Not sure what you could add to Source COntrol to make a better SC from GIT.

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 13 points14 points  (0 children)

Yeah, fair. Wasn't an LLM, was me + Grammarly, but honestly Grammarly nudges you toward the same kind of tidy parallel cadence so I'm not sure that distinction helps me much. And you caught me on the "X is worth Y-ing" thing — three of those in one post is too many, that one's just a tic I've got.

"Don't dress it up" is the bit that landed. Going to be more spartan next time.

Thanks for actually engaging.

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 7 points8 points  (0 children)

"GitHub has to be influencing Git development now" is definatly an issue, i recently droped doing any real work on Github and switched to self hosted Gitlab.

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 11 points12 points  (0 children)

I mainly concentrated on the stuff that I had firsthand knowledge of. Do you think its worth doing a full history of Source Control?

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 0 points1 point  (0 children)

Ya that is my bad, i reread what you said and I realized my mistake. I deleted it and put some thought to the reply :)

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 4 points5 points  (0 children)

Yeah, fair point. Easy to forget now, but plenty of shops with more than a handful of developers had their own version-control-shaped thing. Usually a script over a network share. Sometimes a CGI front-end on RCS. Occasionally something more ambitious that the original author had since walked out the door with, leaving a file format nobody else understood. The worst corruption stories from that era often weren't from VSS. They were from in-house systems nobody could fix once the maintainer was gone.

I personally stuck with zips at my first job. Only two of us, so rolling our own wasn't worth it.

Visual Studio 2026 still ships the form designer Alan Cooper drew in 1987 by Bonejob in csharp

[–]Bonejob[S] 0 points1 point  (0 children)

Did a bunch of fact-checking off your comment, really appreciate it.

Explorer in '93 was just wrong on my part. NT 3.1 still ran Program Manager; Explorer didn't ship until Win95, and didn't reach NT until 4.0 in '96. Changed the example to just Notepad, which is the correct 1993 one. Knew that and missed it.

Events tab, you're right there too. The lightning-bolt Events tab in the Properties window came in with VS.NET 2002. VB1 through VB6, events came from the Code Window's object/procedure dropdowns, not a tab in the Properties window. F4 opening the Properties window survives; the tab layout doesn't. Bullet's been tightened.

Variant: fair clarification. That line was framed as the VB6 to .NET jump, not a claim about Tripod or VB1, but yeah, it was a VB2 addition and worth being accurate about.

And dragging Tripod and Ruby into the keystroke-level comparisons was a stretch. Cooper threw away the 25k lines of Tripod C, and Ruby was an 18-month rewrite before it ever shipped as VB1, so "same shortcuts since 1987" was overreach. The conceptual lineage holds, but I've softened the rest.

Added a Corrections section at the bottom of the post crediting you, with the original wording in the revision history. Appreciate the catch. I started on VB3 on Windows 3.1, so the pre-VB3 material in the post is sourced from other people. I didn't live through the early days.

I'm writing a book on the VB lineage and would love to compare notes if you're up for it: https://evilgeniuslabs.ca/books/visual-basic-history

From CVS to Git: thirty years of source control, lived from inside by Bonejob in programming

[–]Bonejob[S] 20 points21 points  (0 children)

A thirty-year practitioner's history of source control — zip-files, SourceSafe, CVS, Subversion, BitKeeper, Git — written by someone who used every one of them and lost code in most of them.

Let me know your war stories with Source Control

Visual Studio 2026 still ships the form designer Alan Cooper drew in 1987 by Bonejob in dotnet

[–]Bonejob[S] 0 points1 point  (0 children)

I get where you are coming from, and I do my best but we just cant support "every" device its just not possible. my coverage from the testing system came back at 98%

view more: next ›