I see many negative comments about Microsoft and "yet another UI framework"... I started back in the Webforms/Silverlight days, and brough over my skills to each next iteration and had a pretty pleasant dev. experience ever since.
I was using the following: Silverlight -> WPF -> Windows Phone -> WPF -> Angular/webdev -> Xamarin.Forms and now since MAUI Preview 11, we've been building our new mobile/desktop product with it, and we'll release it soon.
The part where I was a web developer was honestly awful. Web frontend isn't even close to what any of those mentioned above are right now. Layouting stuff on the web is a nightmare, a little less now that grid is coming along, but still lightyears away from what you have in WPF/XF/MAUI... and then there's decoupling UI code from your business logics for testability. With Angular/React/Vue (Vue suted me most, but it's still meh) it's halfway there but still meh.
On the .Net stack, you have battletested frameworks and libraries that have been around for ages, on both, hobbyist apps to full blown enterprise solutions. At some point I was working on a desktop app that would run on a 5*6 monitor array (highway control room software)... 30 windows open in parallel from one app, everything in sync, everything just working 24/7.
And now, we'll cover Android/iOS and Windows desktop, with one codebase, and it's not just a simple CRUD app. We're connecting with RFID readers, using cameras, geo service etc... I can't imagine pulling this off, in the timeframe we did, and the amount of devs working on it, with any other stack.
Yes, there's no Linux support, but the way MAUI is laid out, it shouldn't be too hard to get that going. Just look at who and how contributed the Tizen backend. I'm sure the folks at MS will welcome you with open arms if you want to contribute some effort into making Linux happen.
> Web frontend isn't even close to what any of those mentioned above are right now. Layouting stuff on the web is a nightmare.
One with more experience with web dev can easily submit the exact opposite comment - web layout and tooling are light years ahead of whatever most recent .NET endeavor.
The web is also already cross-platform, where every platform looks and feels native to itself. This announcement doesn't show off a single native macOS or iOS component. Seeing it's inspired/supported by Xamarin, APIs for look & feel are minimal unless you opt for a platform-specific implementation anyway (e.g., the "common" animations API is a fraction of what one requires for a good experience on iOS).
I'm sure MAUI will be famous in enterprise apps where the latest productivity tool needs to be put together quickly and inflicted on employees for years to come (cough* Teams, Office...).
I'd say I'm equally fluent in both because I put heaps of effort into my web dev skills so I could charge the same hourly rate and deliver the same quality I deliver for Desktop/Mobile. I adhere to certain standards when I put my name behind something I deliver to a client.
The amount of "oh yeah, it seems hacky but that's the best practice" on web is mindboggling. Every time I had to use HTML/CSS/JS hacks to achieve something rather simple in terms of laying out components on the screen, I wanted to quit working on the project.
The amount of work you have to put into web frontend to get it pixel perfect and according to the design, is roughly 40-50% more than achieving the same thing on let's say WPF.
Take it however you want, but what MS achieves in dev experience on their UI stacks is quite admirable. The fact that those stacks don't survive long is a another pair of shoes.
If you're operating in a grayish legal area, start worrying about laws once you're so big that your government worries about you. If I did my last startup now, I'd spend all the money I spent on lawyers, on marketing. By the time we had on paper that our business is operating within the law, we were down a big chunk of money that we later desperately needed to gain traction. If you fail, no one will care to sue you anyway (specially not your government). But if you make it, you'll have money for lawyers and money to eventually make it more legally acceptable.
I used the like/dislike ratio to see if something is actually a good video about the topic I'm searching, or should I continue further.
For example, if I search "volvo s40 MAF sensor replacement", I won't watch someone ramble 20 minutes about how volvos are good, and why they chose the car in white instead of blue color... I want someone who'll pop the hood and replace the sensor, and those videos will usually have a better like/dislike ratio compared to the random rambling videos.
The ratio was the telling thing if a "how to" video was good. I'd rather watch a video that has only 100 likes, but 0 dislikes, than a video that has 1000 likes and 5000 dislikes. But now that's gone, R.I.P.
Apparently some previously-scrapped data for older videos that gets updated, and heuristic estimates combined with extrapolating data from those who use that extension and like/dislike. LTT did a video where they found the accuracy really good.
Beating Google at their own game, they (apparently) are.
I think the accuracy doesn't even matter too much. Personally, I believe I base my decision to watch the video after clicking on it on the ballpark the like/dislike ratio is in. "Almost only likes", "2/3 likes", "50/50 likes/dislikes", ... For that purpose, the extension does its job.
> with extrapolating data from those who use that extension and like/dislike.
Often you see the opposite, where a third party service provides customers with a feature extending the features of a big service like youtube or twitter, and then the big service buys the startup offering that extension, or integrates the feature themselves, leaving the extension dead. Now we see it happening in reverse direction, very interesting.
Apparently, the Youtube API documented here - https://developers.google.com/youtube/v3/docs/videos - returns both likes and dislikes. All Google did was remove the rendering of that API response field onto the webpage.
Extensions probably acquire the video url and make their own API call just to retrieve the dislike count. To me, that seems cleaner than trying to snoop on the main API call response (I think extensions might not have access to those, maybe they do). Basically, the data is available via API calls.
That's the analytics API. We already know they show dislikes to the channel owner. Isn't this the same thing?
And your other comment says "The dislike count is also still present in the [0] video API response." but the page says right there "Note: The statistics.dislikeCount property was made private as of December 13, 2021."
Since they removed the dislike count, I've watched zero technical/programming and related videos on youtube. I'm not going to sit for 30 minutes and then realise the video is a pile of garbage.
I'm amazed that anyone can find any decent programming content on YouTube. There are low-quality beginners webdev tutorials as far as the eye can see, but otherwise there's seemingly very little outside of rambling and superficial conference talks. And on the odd occasion when I do watch a video, YouTube decides that I must be a beginning webdev and bombards me with the aforementioned low-quality Javascript and HTML tutorials for the next several weeks.
Uhhh, the reasoning is such a slippery slope and will end up sowing more division among us. I wouldn't be mad at any unvaccinated person who would withdraw themselves as an organ donor due to this. Can't get, won't give. Fair play.
We live in such broken times, I hope we can bounce back from this, but I only see more and more fragmentation.
Long time lurker here, first time poster. I got pulled into the rabbit hole of building guitars at home during the covid lockdowns. My first build used traditional "tonewoods" (mahogany, ebony, rosewood etc.) and while purchasing materials for my second build, I stumbled upon bamboo boards on a German wood retailed shop.
Compared the properties to the wood I wanted to use for parts of it (mainly the core/neck and fretboard) and decided to go for it.
So the second build [1] is 40ish % bamboo with purpleheart veneers in between layers of bamboo and purpleheart/olive for the body. Next build will be around 80% bamboo. Trying to source some strand woven bamboo boards to try them out as fretboards as well, but for a part time builder like me, getting such small quantities of bamboo boards is rather hard.
But yeah, fascinating material even outside of construction use. The boards I used for the guitar builds were nice to work with, easy to sand and finish (using wipe on poly).
One of the themes in this thread is reminding people that it's not actually bamboo, it's a bamboo composite--sort of like plywood. I doesn't work without petrochemical glues.
I think it's fairer to say your build is 40%-ish bamboo composite. When we're calling it bamboo we're doing that industry's greenwashing marketing for them.
If the mentioned bamboo composite is 95% bamboo and 5% glue (going by comment from hwillis), isn't it fair to say it's 40%-ish bamboo?
5% glue is far from something like carbon composite, where most content is epoxy. Common wood surface treatment is probably more than 5%, yet we don't call it a wood composite.
IMO, total surface sealant makes more of a material difference than 5% glue on the inside.
I appreciate the viewpoint, but we don't call plywood "wood" because it isn't wood. If we were to develop a metric, the % of mass of the finished product that isn't wood would be a reasonable one.
The problem with saying it's 38% bamboo is it implies it's in some meaningful sense made out of bamboo. It's not. There isn't a way to go in there and cut out a piece and have it be bamboo--unless it's really, really small (maybe). Whereas it's totally possible to take a piece of wood from an old piece of furniture, surface it four sides, and have essentially wood (albeit a little smaller).
I think also that you're a little off on two things: 1, common wood surface treatments are < 5%, and 2, composites vary but 60/40 fiber/resin by mass is a reasonable place to start.
Some of the terms being used are getting more and more ‘artistic’ too - I’ve seen a lot more use of the term ‘manufactured wood’ for instance, and like you’re noting hybrid ‘core is mdf, edges are real wood, top is veneer’ type stuff that you have to dig to find out, and that is way more complicated than the ‘traditional’ mdf+veneer junk.
The edge-glued boards at Menards are quite good - they're foot wide "shelves" if you will made from glued 4 inch wide pieces; they work and are roughly as strong as normal boards at a cheaper price - and come finished.
Edge-gluing's one technique you'll find in woodworking books, for making large surfaces. Desktops or table tops made out of a single piece of lumber are wicked expensive, or practically impossible once you reach a certain size, so you join a bunch of smaller boards to make it happen. The really cheap & easy version of this skips the gluing and just frames them so they're smushed together, leaving visible seams and gaps like a slightly-tighter version of an outdoor picnic table (I've even seen this look imitated by solid table tops made from particle board and veneer, which... WTF? Those seams are crumb-traps! They make dealing cards a pain in the ass! Why would you go out of your way to have them?), but the better kind involves gluing.
I used one of their planed, unfinished edge-glued boards when I built my kid's bassinet. I was impressed by the uniform quality; it was almost as if it was a single board. Thanks Menards! (Full disclosure, my employer is technically a competitor, but we don't sell lumber.)
I noticed you use the Planet Waves tuners. I love those as well, they're much more practical as they cut the strings for you. I wonder why they don't make them in more traditional colors, or why other manufacturers don't provide similar solutions. Everyone else makes just regular and locking tuners, not the locking-and-cutting tuners.
For a performing amateur musician, the ability to change your string quicker and without having to carry extra tools is certainly beneficial, and people spend a lot of time fretting about much less important details in their guitars.
I do like the current trend in youtube guitar videos talking more about playability, usability and reliability, and doing things like switching jacks or nuts, instead of endless pickup sound comparisons.
Yeah, I was looking into buying a new instrument, then youtube started suggesting all those build videos. Eventually found the project guitar web/forums and went for it. Probably my favorite side projects so far.
May I ask what you paid in the end for the bamboo you used? I went down the same rabbit hole some time ago and in the end went with oak as it was a lot more affordable (for my student budget back then).
121x20 cm board, 20mm thick was around 22 EUR + shipping. The shop I bought it from had 3 kinds of bamboo boards (normal, dark and some "figured" made up of dark and light stripes) but currently sell only the figured.
I guess I was looking in the wrong places ... or the wrong construction. 20 mm thick sounds like it was only the core with more layers.
In the end I went with some 150x4cm oak strips of varying width from the left-overs bin of a wood vendor. 5€ the piece was a pretty good deal back then.
Yeah, I cut the board I ordered into 4 stripes, rotated them for 90 degrees and glued back together with purpleheart veneer in between, to get the core/neck part.
I really wanna build one almost completely from bamboo (with various veneers to get some accents/lines in) but it's really hard to source boards now. Meh... but yeah, who would have thought that "tonegrass" would become a term someday haha.
I honestly believe that the key to building a good guitar is stiffness ... This will create a very high pitched instrument, as it does not lose the high frequencies in the wood. But that can be sorted out later vis EQing
I always thought that hardness is most important in a fretboard, is bamboo hard enough for this? I have a Parker guitar with a glass composite fretboard (carbon glass they call it) and it’s the best part of the guitar for playability.
The bamboo boards I ordered had a higher density than ebony (1100 kg/m^3 for bamboo vs. 955 kg/m^3 for ebony) and according to the suppliers site, they are roughly the same Janka hardness. That's why I went for it.
I don’t know if hardness is the best criteria. I have both rosewood and ebony fretboards on my basses and they feel differently and longevity seems only loosely affected. I’m not slamming down hard on the wood like what happens in flooring though and maybe other players are much rougher than myself.
Keep in mind these aren’t what you would get if you cut down some bamboo and used them. They’re usually processed, compressed, and a high % by weight of glue or epoxy. Many of them are harder and tougher than all but a tiny percent of exotic hard woods.
I was using the following: Silverlight -> WPF -> Windows Phone -> WPF -> Angular/webdev -> Xamarin.Forms and now since MAUI Preview 11, we've been building our new mobile/desktop product with it, and we'll release it soon.
The part where I was a web developer was honestly awful. Web frontend isn't even close to what any of those mentioned above are right now. Layouting stuff on the web is a nightmare, a little less now that grid is coming along, but still lightyears away from what you have in WPF/XF/MAUI... and then there's decoupling UI code from your business logics for testability. With Angular/React/Vue (Vue suted me most, but it's still meh) it's halfway there but still meh.
On the .Net stack, you have battletested frameworks and libraries that have been around for ages, on both, hobbyist apps to full blown enterprise solutions. At some point I was working on a desktop app that would run on a 5*6 monitor array (highway control room software)... 30 windows open in parallel from one app, everything in sync, everything just working 24/7. And now, we'll cover Android/iOS and Windows desktop, with one codebase, and it's not just a simple CRUD app. We're connecting with RFID readers, using cameras, geo service etc... I can't imagine pulling this off, in the timeframe we did, and the amount of devs working on it, with any other stack.
Yes, there's no Linux support, but the way MAUI is laid out, it shouldn't be too hard to get that going. Just look at who and how contributed the Tizen backend. I'm sure the folks at MS will welcome you with open arms if you want to contribute some effort into making Linux happen.